1 |
Opening of the meeting |
|
R2-2008137 |
(reserved) |
nn |
R2-2008465 |
(reserved) |
nn |
2.1 |
Approval of the agenda |
|
R2-2006500 |
Agenda for RAN2#111-e |
Chairman |
2.2 |
Approval of the report of the previous meeting |
|
R2-2006501 |
RAN2#110bis-e Meeting Report |
MCC |
2.4 |
Others |
|
R2-2008391 |
RAN2#111-e Meeting Guidelines |
MCC |
R2-2008652 |
Inter-system direct forwarding with shared en-gNB/gNB |
R3 (Nokia, Nokia Shanghai Bell, Samsung, CATT, China Telecom, Huawei, Ericsson) |
R2-2008653 |
Correction for Industrial IoT PDCP duplication for Carrier Aggregation |
R3 (Intel Corporation, CATT, Huawei, Ericsson) |
R2-2008654 |
Correction for Industrial IoT PDCP duplication for Carrier Aggregation |
R3 (Intel Corporation, CATT, Huawei, Ericsson) |
R2-2008655 |
Introducing UE Radio Capability Mapping procedure for EN-DC |
R3 (Huawei, CATT, Samsung, Ericsson) |
R2-2008656 |
Introducing UE Radio Capability Mapping procedure for EN-DC |
R3 (Huawei, CATT, Samsung, Ericsson) |
R2-2008657 |
Correction of NPN CAG cells and non-CAG cells |
R3 (Nokia, Nokia Shanghai Bell, Orange) |
R2-2008658 |
Introduction of NR positioning |
R3 (Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Intel, Qualcomm) |
R2-2008672 |
Further correction for CA-based PDCP duplication for Industrial IoT |
Intel Corporation, CATT, Huawei, Ericsson, ZTE Corporation (Rapporteur) |
R2-2008673 |
Correction for CA-based PDCP duplication |
Intel Corporation, CATT, Huawei, Ericsson, ZTE Corporation (Rapporteur) |
R2-2008676 |
Introducing UE Radio Capability Mapping procedure for EN-DC |
R3 (Huawei, CATT, Samsung, Ericsson) |
R2-2008677 |
Introducing UE Radio Capability Mapping procedure for EN-DC |
R3 (Huawei, CATT, Samsung, Ericsson) |
4.1 |
NB-IoT corrections Rel-15 and earlier |
|
R2-2006838 |
36331_R15_Clarification for NPRACH carrier selection |
ZTE Corporation, Sanechips, MediaTek Inc |
R2-2006840 |
36331_R16_Clarification for NPRACH carrier selection |
ZTE Corporation, Sanechips, MediaTek Inc |
R2-2007330 |
System support for Wake Up Signal |
Huawei, HiSilicon |
R2-2007331 |
System support for Wake Up Signal |
Huawei, HiSilicon |
R2-2007332 |
System support for Wake Up Signal |
Huawei, HiSilicon |
R2-2007333 |
System support for Wake Up Signal |
Huawei, HiSilicon |
R2-2007334 |
Discussion of WUS last used cell |
Huawei, HiSilicon |
R2-2007566 |
Way forward on WUS usage upon RRC connection release without S1 setup/release |
Qualcomm Incorporated |
R2-2008301 |
Report of [AT111-e][301][NBIOT R15] NPRACH carrier selection (ZTE) |
ZTE (email discussion rapporteur) |
R2-2008302 |
Offline [AT111-e][302][NBIOT/eMTC R15] WUS last used cell (Huawei) |
Huawei (offline email discussion rapporteur) |
R2-2008544 |
Reply LS on system support for WUS (S2-2006478; contact: Qualcomm) |
SA2 |
R2-2008550 |
Reply LS on assistance indication for WUS (S2-2006499; contact: Qualcomm) |
SA2 |
R2-2008588 |
System support for Wake Up Signal |
Huawei, HiSilicon |
R2-2008589 |
System support for Wake Up Signal |
Huawei, HiSilicon |
R2-2008590 |
System support for Wake Up Signal |
Huawei, HiSilicon |
R2-2008591 |
System support for Wake Up Signal |
Huawei, HiSilicon |
R2-2008592 |
System support for Wake Up Signal |
Huawei, HiSilicon |
R2-2008593 |
System support for Wake Up Signal |
Huawei, HiSilicon |
4.2 |
eMTC corrections Rel-15 and earlier |
|
R2-2007327 |
Discussion of UP EDT for DRB using RLC AM |
Huawei, HiSilicon |
R2-2007328 |
Clarification to UP-EDT |
Huawei, HiSilicon |
R2-2007329 |
Clarification to UP-EDT |
Huawei, HiSilicon |
R2-2008232 |
Report of [AT111-e][402][NB-IoT/eMTC R15] UP EDT for DRB using RLC AM (Huawei) |
Huawei (offline email discussion rapporteur) |
R2-2008239 |
Report of [AT111-e][402][NB-IoT/eMTC R15] UP EDT for DRB using RLC AM (Huawei) |
Huawei (offline email discussion rapporteur) |
4.3 |
V2X and Sidelink corrections Rel-15 and earlier |
|
R2-2006777 |
Corrections to data inactivity monitoring considering SL logical channels |
Samsung Electronics Co., Ltd |
R2-2006778 |
Corrections to data inactivity monitoring considering SL logical channels |
Samsung Electronics Co., Ltd |
R2-2007898 |
Sidelink synchronization ID |
Qualcomm Finland RFFE Oy, Apple, Ericsson, Kyocera, ZTE, CATT, InterDigital, Lenovo, Motorola Mobility |
R2-2008352 |
Sidelink synchronization ID |
Qualcomm Finland RFFE Oy, Apple, Ericsson, Kyocera, ZTE, CATT, InterDigital, Lenovo, Motorola Mobility |
R2-2008404 |
CR to 36.331 on SLSS ID |
Qualcomm, Ericsson, Apple, Kyocera, ZTE, CATT, InterDigital, Lenovo, Motorola Mobility |
R2-2008582 |
CR to 36.331 on SLSS ID |
Qualcomm, Ericsson, Apple, Kyocera, ZTE, CATT, InterDigital, Lenovo, Motorola Mobility, Nokia, Intel Corporation |
4.4 |
Positioning corrections Rel-15 and earlier |
|
R2-2008051 |
UE E-CID measurement reporting |
Nokia, Nokia Shanghai Bell |
R2-2008257 |
UE E-CID measurement reporting |
Nokia, Nokia Shanghai Bell |
R2-2008259 |
UE E-CID measurement reporting |
Nokia, Nokia Shanghai Bell |
4.5 |
Other LTE corrections Rel-15 and earlier |
|
R2-2007517 |
Summary on [Post110e-][255][LTE CA] Clarification on non-contiguous CA capabilities (Nokia) |
Nokia, Nokia Shanghai Bell |
R2-2007554 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
R2-2007555 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
R2-2007556 |
Report of [Post110-e][254][LTE Capa] TDD/FDD differentiation or Rel-15 and earlier (Huawei) |
Huawei, HiSilicon |
R2-2007579 |
Corrections on idle mode measurements |
Ericsson |
R2-2007580 |
Corrections on idle mode measurements |
Ericsson |
R2-2007589 |
Corrections on idle mode measurements |
Ericsson Inc. |
R2-2007719 |
Correction on PDU generation for UL spatial multiplexing – Option 1 |
ASUSTeK |
R2-2007720 |
Correction on PDU generation for UL spatial multiplexing – Option 2 |
ASUSTeK |
R2-2007721 |
Correction on PDU generation for UL spatial multiplexing – Option 1 |
ASUSTeK |
R2-2007722 |
Correction on PDU generation for UL spatial multiplexing – Option 2 |
ASUSTeK |
R2-2007723 |
Correction on PDU generation for UL spatial multiplexing – Option 1 |
ASUSTeK |
R2-2007724 |
Correction on PDU generation for UL spatial multiplexing – Option 2 |
ASUSTeK |
R2-2007843 |
Minor changes collected by Rapporteur |
Samsung |
R2-2008022 |
ROHC decompression failure at PDCP re-establishment |
Samsung |
R2-2008023 |
CR on PDCP re-establishment when t-Reordering is used |
Samsung |
R2-2008027 |
CR on PDCP re-establishment when t-Reordering is used |
Samsung |
R2-2008131 |
Summary of offline 201 - LTE Miscellaneous Rel-15/16 corrections |
Samsung |
R2-2008152 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
R2-2008153 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
R2-2008154 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
R2-2008155 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
R2-2008156 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
R2-2008157 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
R2-2008158 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
R2-2008159 |
Minor changes collected by Rapporteur |
Samsung |
R2-2008161 |
Corrections on idle mode measurements |
Ericsson |
R2-2008162 |
Corrections on idle mode measurements |
Ericsson |
R2-2008163 |
Corrections on idle mode measurements |
Ericsson Inc. |
R2-2008164 |
Corrections on idle mode measurements |
Ericsson Inc. |
R2-2008171 |
LS on Incomplete LTE Physical Layer Capabilities |
RAN2 |
R2-2008242 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
R2-2008243 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
R2-2008244 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
R2-2008245 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
R2-2008246 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Nokia, Nokia Shanghai Bell |
5.1 |
Organisational |
|
R2-2008623 |
LS on PUSCH with UL skipping (R1-2007338; contact: vivo) |
RAN1 |
5.2.1 |
TS 3x.300 |
|
R2-2006870 |
Clarification on NCGI |
ZTE corporation, Sanechips, Nokia (Rapporteur) |
R2-2007030 |
Discussion on regional Public Warning Systems |
Huawei, HiSilicon |
R2-2007031 |
Clarification on regional Public Warning Systems |
Huawei, HiSilicon |
R2-2007032 |
Clarification on regional Public Warning Systems |
Huawei, HiSilicon |
R2-2007222 |
Correction on Timing advance group related clarification |
vivo |
R2-2007223 |
Correction on Timing advance group related clarification |
vivo |
R2-2008425 |
Summary of offline 001 - NR Stage 2 corrections |
ZTE |
5.3.1 |
MAC |
|
R2-2006657 |
Clarification on operations in a bundle of UL grants |
Samsung |
R2-2006680 |
Correction to SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE handling |
Samsung |
R2-2006681 |
Correction to SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE handling |
Samsung |
R2-2007135 |
Clarification on HARQ process ID determination for SPS |
OPPO, Samsung |
R2-2007136 |
Clarification on HARQ process ID determination for SPS |
OPPO, Samsung |
R2-2007725 |
DRX with bundle transmission of configured uplink grant |
ASUSTeK |
R2-2007726 |
Correction on DRX with bundle transmission of configured uplink grant |
ASUSTeK |
R2-2007727 |
Correction on DRX with bundle transmission of configured uplink grant |
ASUSTeK |
R2-2007861 |
Clarification on collision between uplink grant for MSG3 retransmission and DG |
Huawei, HiSilicon |
R2-2007897 |
Correction to not (re)starting drx-InactivityTimer when dynamic grant is skipped |
MediaTek Inc. |
R2-2007899 |
Correction to not (re)starting drx-InactivityTimer when dynamic grant is skipped |
MediaTek Inc. |
R2-2008485 |
Clarification on HARQ process ID determination for SPS |
OPPO, Samsung |
R2-2008486 |
Clarification on HARQ process ID determination for SPS |
OPPO, Samsung |
5.3.3 |
PDCP |
|
R2-2007059 |
38323 CR PDCP entity associated with AM RLC entity |
LG Electronics Inc., Ericsson |
R2-2007060 |
38323 CR PDCP entity associated with AM RLC entity |
LG Electronics Inc., Ericsson |
R2-2008418 |
PDCP entity associated with AM RLC entity |
LG Electronics Inc., Ericsson |
R2-2008419 |
PDCP entity associated with AM RLC entity |
LG Electronics Inc., Ericsson |
5.4.1.1 |
Connection control |
|
R2-2006683 |
Correction on aperiodicSRS resource |
vivo |
R2-2006889 |
CR on condition of SyncAndCellAdd |
ZTE Corporation, Sanechips |
R2-2006890 |
CR on condition of SyncAndCellAdd |
ZTE Corporation, Sanechips |
R2-2006891 |
CR to clarify UE behaviour after TAT expiry due to reconfigurationWithSync |
ZTE Corporation, Sanechips |
R2-2006892 |
CR to clarify UE behaviour after TAT expiry due to reconfigurationWithSync |
ZTE Corporation, Sanechips |
R2-2006986 |
Further correction on UEAssistanceInformation upon reconfiguration with sync |
CATT |
R2-2006987 |
Further correction on UEAssistanceInformation upon reconfiguration with sync |
CATT |
R2-2006993 |
Correction on Presence Condition of securityConfig |
CATT |
R2-2006994 |
Correction on Presence Condition of securityConfig |
CATT |
R2-2006995 |
Correction on the Cross Carrier Scheduling Configuration |
CATT |
R2-2006996 |
Correction on the Cross Carrier Scheduling Configuration |
CATT |
R2-2007057 |
Clarification on the absence of pathlossReferenceRSs |
Huawei, HiSilicon |
R2-2007058 |
Clarification on the absence of pathlossReferenceRSs |
Huawei, HiSilicon |
R2-2007121 |
Clarification on the UE dedicated configuration of rlf-TimersAndConstants |
Apple |
R2-2007122 |
Clarification on the UE dedicated configuration of rlf-TimersAndConstants |
Apple |
R2-2007264 |
Incorrect creation of SCG MAC entity |
Ericsson |
R2-2007265 |
Incorrect creation of SCG MAC entity |
Ericsson |
R2-2007348 |
Clarification on NR PDCP COUNT wrap around |
Nokia, Nokia Shanghai Bell |
R2-2007349 |
Clarification on NR PDCP COUNT wrap around |
Nokia, Nokia Shanghai Bell |
R2-2007504 |
Correction on aperiodicSRS resource |
vivo |
R2-2008038 |
Reconfiguring RoHC and setting the drb-ContinueROHC simultaneously |
Qualcomm Incorporated |
R2-2008039 |
Reconfiguring RoHC and setting the drb-ContinueROHC simultaneously |
Qualcomm Incorporated |
R2-2008042 |
SIB1 to include all supported channel bandwidths by the gNB |
Qualcomm Incorporated |
R2-2008086 |
Clarification on the SRB configuration for fullConfig during RRC Resume procedure (R15) |
ZTE corporation, Sanechips |
R2-2008087 |
Clarification on the SRB configuration for fullConfig during RRC Resume procedure (R16) |
ZTE corporation, Sanechips |
R2-2008091 |
Clarification on re-establishment procedure (R15) |
ZTE corporation, Sanechips |
R2-2008092 |
Clarification on re-establishment procedure (R16) |
ZTE corporation, Sanechips |
R2-2008293 |
Reconfiguring RoHC and setting the drb-ContinueROHC simultaneously |
Qualcomm Incorporated |
R2-2008423 |
Report of [AT111-e][005][NR15] Misc Configuration. |
ZTE |
R2-2008469 |
CR to clarify UE behaviour after TAT expiry caused by reconfigurationWithSync |
ZTE Corporation, Sanechips |
R2-2008470 |
CR to clarify UE behaviour after TAT expiry due to reconfigurationWithSync |
ZTE Corporation, Sanechips |
R2-2008471 |
CR on SyncAndCellAdd condition |
ZTE Corporation, Sanechips |
R2-2008472 |
CR on SyncAndCellAdd condition |
ZTE Corporation, Sanechips |
R2-2008473 |
Clarification on the SRB configuration for fullConfig during RRC Resume procedure |
ZTE corporation, Sanechips |
R2-2008474 |
Clarification on the SRB configuration for fullConfig during RRC Resume procedure |
ZTE corporation, Sanechips |
R2-2008476 |
Report of ?[AT111-e][004][NR15] L2 Parameters and Security (CATT)? |
CATT |
R2-2008526 |
Correction on the Cross Carrier Scheduling Configuration |
CATT |
R2-2008527 |
Correction on the Cross Carrier Scheduling Configuration |
CATT |
R2-2008596 |
Summary of offline discussion #003: NR L1 Parameters |
vivo |
5.4.1.2 |
RRM and Measurements and Measurement Coordination |
|
R2-2006676 |
Clarification of measCycleSCell in measObjectNR |
NTT DOCOMO INC. |
R2-2006677 |
Clarification of measCycleSCell in measObjectNR |
NTT DOCOMO INC. |
R2-2008447 |
Offline-006[NR15] Measurements and System Information |
ZTE Corporation, Sanechips |
5.4.1.3 |
System information |
|
R2-2007405 |
Clarification on network specific uac-AccessCategory1-SelectionAssistanceInfo |
ZTE corporation, Sanechips, CMCC |
R2-2007406 |
draft CR on network specific uac-AccessCategory1-SelectionAssistanceInfo in TS38.331-R15 solution |
ZTE corporation, Sanechips, CMCC |
R2-2007407 |
draft CR on network specific uac-AccessCategory1-SelectionAssistanceInfo in TS36.331-R15 solution |
ZTE corporation, Sanechips, CMCC |
R2-2007408 |
draft CR on network specific uac-AccessCategory1-SelectionAssistanceInfo in TS38.331-R16 solution |
ZTE corporation, Sanechips, CMCC, Nokia |
R2-2007409 |
draft CR on network specific uac-AccessCategory1-SelectionAssistanceInfo in TS36.331-R16 solution |
ZTE corporation, Sanechips, CMCC, Nokia |
R2-2007410 |
[Draft] LS on UAC Access Category 1 selection |
ZTE corporation, Sanechips |
5.4.1.4 |
Inter-Node RRC messages |
|
R2-2007674 |
Clarification on scg-RB-Config |
Huawei, HiSilicon |
R2-2007675 |
Clarification on scg-RB-Config |
Huawei, HiSilicon |
R2-2008412 |
Summary of [AT111-e][007][NR15] Inter Node and NR Misc |
Ericsson |
5.4.1.5 |
Other |
|
R2-2006878 |
Network-specific access barring for delay tolerant service |
Lenovo, Motorola Mobility |
R2-2006999 |
Corrections Based on the Rule of Field and IE Usage |
CATT |
R2-2007000 |
Corrections Based on the Rule of Field and IE Usage |
CATT |
R2-2007253 |
Clarification for KPAS and EU-alert |
Ericsson, Nokia |
R2-2007254 |
Clarification for KPAS and EU-alert |
Ericsson, Nokia |
R2-2007255 |
Clarification for KPAS and EU-alert |
Ericsson, Nokia |
R2-2007256 |
Clarification for KPAS and EU-alert 38.331 |
Ericsson, Nokia |
R2-2007257 |
Clarification for KPAS and EU-alert 38.331 |
Ericsson, Nokia |
R2-2007643 |
Miscellaneous non-controversial corrections Set VII |
Ericsson |
R2-2007644 |
Miscellaneous non-controversial corrections Set VII |
Ericsson |
R2-2007792 |
Correction on condition of stopping overheating prohibit timer |
Huawei, HiSilicon |
R2-2007793 |
Correction on condition of stopping overheating prohibit timer |
Huawei, HiSilicon |
R2-2007794 |
Correction on UE assistance information transmission for handover case |
Huawei, HiSilicon |
R2-2007795 |
Correction on UE assistance information transmission for handover case |
Huawei, HiSilicon |
R2-2008531 |
Summary of offline 008 – NR UAI |
Huawei, HiSilicon |
R2-2008532 |
Correction on UE assistance information transmission for handover case |
Huawei, HiSilicon |
R2-2008533 |
Correction on UE assistance information transmission for handover case |
Huawei, HiSilicon |
R2-2008605 |
Miscellaneous non-controversial corrections Set VII |
Ericsson |
R2-2008606 |
Miscellaneous non-controversial corrections Set VII |
Ericsson |
5.4.2 |
LTE changes related to NR |
|
R2-2006997 |
Correction on the Presence Condition for drb-ToAddModList |
CATT |
R2-2006998 |
Correction on the Presence Condition for drb-ToAddModList |
CATT |
R2-2007350 |
Clarification about UL 256QAM |
Nokia, Nokia Shanghai Bell |
R2-2007351 |
Clarification about UL 256QAM |
Nokia, Nokia Shanghai Bell |
R2-2008083 |
Problem on SI scheduling via an extended field |
NTT DOCOMO, INC. |
R2-2008107 |
Workaround for LTE SIB24 issue |
MediaTek |
R2-2008408 |
[AT111-e][042][NR15] LTE Other (Nokia) |
Nokia |
R2-2008410 |
Clarification on UL 256QAM |
Nokia, Nokia Shanghai Bell |
R2-2008411 |
Clarification on UL 256QAM |
Nokia, Nokia Shanghai Bell |
R2-2008427 |
Report of email discussion [AT111-e][009][NR15] LTE SIB extension issue |
NTT DOCOMO, INC. (Email discussion rapporteur) |
R2-2008488 |
Correction on the Presence Condition for drb-ToAddModList |
CATT |
R2-2008489 |
Correction on the Presence Condition for drb-ToAddModList |
CATT |
R2-2008664 |
Modification of SI scheduling for extended SIBs |
NTT DOCOMO, INC. |
R2-2008665 |
Modification of SI scheduling for extended SIBs |
NTT DOCOMO, INC. |
R2-2008666 |
Modification of SI scheduling for extended SIBs |
NTT DOCOMO, INC. |
R2-2008667 |
Modification of SI scheduling for extended SIBs |
NTT DOCOMO, INC. |
R2-2008668 |
Modification of SI scheduling for extended SIBs |
NTT DOCOMO, INC. |
R2-2008675 |
Correction on the Presence Condition for drb-ToAddModList |
CATT |
5.4.3 |
UE capabilities and Capability Coordination |
|
R2-2007084 |
Clarification on CGI reporting in EN-DC and NE-DC |
Apple |
R2-2007209 |
Clarification on the BandCombination |
ZTE Corporation, Sanechips |
R2-2007210 |
CR on the BandCombination (R15) |
ZTE Corporation, Sanechips |
R2-2007211 |
CR on the BandCombination (R16) |
ZTE Corporation, Sanechips |
R2-2007212 |
CR on support of 35MHz and 45MHz channel bandwidth (R15) |
ZTE Corporation, Sanechips |
R2-2007213 |
CR on support of 35MHz and 45MHz channel bandwidth (R16) |
ZTE Corporation, Sanechips |
R2-2007303 |
Corrections on UE capability constraints |
vivo |
R2-2007304 |
Corrections on UE capability constraints |
vivo |
R2-2007305 |
Corrections on UE capability constraints |
vivo |
R2-2007306 |
Corrections on UE capability constraints |
vivo |
R2-2007796 |
Clarification on PDSCH rate-matching capabilities |
Huawei, HiSilicon |
R2-2007797 |
Clarification on PDSCH rate-matching capabilities |
Huawei, HiSilicon |
R2-2007798 |
Discussion on the ambiguity for the capabilities associated with multiple bands/Cells |
Huawei, HiSilicon |
R2-2007799 |
Corrections on the capabilities associated with multiple bands/Cells |
Huawei, HiSilicon |
R2-2007800 |
Corrections on the capabilities associated with multiple bands/Cells |
Huawei, HiSilicon |
R2-2007850 |
xDD and FRx differentiation on UE capabilities which are not signalled by ENUMERATED {supported} |
Samsung |
R2-2007885 |
Clarification on the simultaneousRxTxInterBandCA capability in NR-DC |
MediaTek Inc. |
R2-2007887 |
Clarification on the simultaneousRxTxInterBandCA capability in NR-DC |
MediaTek Inc. |
R2-2008290 |
CR on the BandCombination (R15) |
ZTE Corporation, Sanechips |
R2-2008291 |
CR on the BandCombination (R16) |
ZTE Corporation, Sanechips |
R2-2008368 |
Discussion on the ambiguity for the capabilities associated with multiple bands/Cells |
Huawei, HiSilicon |
R2-2008369 |
Corrections on the capabilities associated with multiple bands/Cells |
Huawei, HiSilicon |
R2-2008370 |
Corrections on the capabilities associated with multiple bands/Cells |
Huawei, HiSilicon |
R2-2008421 |
Summary of [AT111-e][011][NR15] UE cap Additions |
vivo |
R2-2008428 |
Summary of offline 010 Rel-15 UE cap Clarifications |
Huawei, HiSilicon |
R2-2008429 |
Corrections on the capabilities associated with multiple bands/Cells |
Huawei, HiSilicon, Ericsson |
R2-2008430 |
Corrections on the capabilities associated with multiple bands/Cells |
Huawei, HiSilicon, Ericsson |
R2-2008431 |
Clarification on PDSCH rate-matching capabilities |
Huawei, HiSilicon |
R2-2008432 |
Clarification on PDSCH rate-matching capabilities |
Huawei, HiSilicon |
R2-2008522 |
Corrections on UE capability constraints |
vivo |
R2-2008523 |
Corrections on UE capability constraints |
vivo |
R2-2008534 |
LS on simultaneous Rx/Tx for inter-band NR-DC |
MediaTek |
R2-2008602 |
Clarification on the extended capability of NGEN-DC |
vivo |
R2-2008635 |
LS on simultaneous Rx/Tx for inter-band NR-DC |
RAN2 |
R2-2008683 |
Clarification on the extended capability of NGEN-DC |
vivo |
5.4.4 |
Idle/inactive mode procedures |
|
R2-2007064 |
Corrections to 36.304 |
Nokia, Nokia Shanghai Bell |
R2-2007097 |
Correction on suitable cell definition |
Apple |
R2-2007119 |
Srxlev Calculation for IRAT Cell Reselection |
Apple, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips, CATT |
R2-2007120 |
Srxlev Calculation for IRAT Cell Reselection |
Apple, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips, CATT |
R2-2008040 |
Correction for Qrxlevmin description in SIB24 |
Qualcomm Incorporated |
R2-2008041 |
Correction for Qrxlevmin description in SIB24 |
Qualcomm Incorporated |
R2-2008481 |
Correction on Srxlev calculation for IRAT Cell Reselection |
Apple, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips, CATT |
R2-2008482 |
Correction on Srxlev calculation for IRAT Cell Reselection |
Apple, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips, CATT |
R2-2008490 |
Corrections to 36.304 |
Nokia, Nokia Shanghai Bell |
R2-2008500 |
Correction for Qrxlevmin description in SIB24 |
Qualcomm Incorporated |
R2-2008501 |
Correction for Qrxlevmin description in SIB24 |
Qualcomm Incorporated |
5.5 |
Positioning corrections |
|
R2-2006665 |
Correction on 38.305 in Table 4.3-1Supported versions of UE positioning methods |
CATT |
R2-2006666 |
Correction on 38.305 in Table 4.3-1Supported versions of UE positioning methods |
CATT |
R2-2006667 |
Correction on 36.305 in Table 4.3-1Supported versions of UE positioning methods |
CATT |
R2-2006668 |
Correction on 36.305 in Table 4.3-1Supported versions of UE positioning methods |
CATT |
6.1.1 |
Cross WI RRC corrections |
|
R2-2006755 |
Correction on on-demand SI in RRC_CONNECTED |
CATT |
R2-2006915 |
Extension scenarios for ToAddMod lists |
MediaTek Inc. |
R2-2006934 |
Handling of CPC in fast MCG recovery |
Intel Corporation |
R2-2007076 |
Corrections to acquisition of posSIB(s) in RRC_CONNECTED |
Samsung Electronics Co., Ltd |
R2-2007275 |
Miscellaneous correction regarding on demand SIB in CONNECTED |
Ericsson |
R2-2007276 |
Redundant procedural text of on demand SIB in CONNECTED |
Ericsson |
R2-2007942 |
ASN.1 issue on uac-AccessCategory1-SelectionAssistanceInfo |
vivo |
R2-2007943 |
38.331 CR for uac-AccessCategory1-SelectionAssistanceInfo |
vivo |
R2-2007944 |
36.331 CR for eab-Param |
vivo |
R2-2008109 |
Correction on DLInformationTransferMRDC and RRCReconfigurationComplete |
Samsung |
R2-2008388 |
Handling of CPC in fast MCG recovery |
Intel Corporation |
R2-2008390 |
Handling of CPC in fast MCG recovery |
Intel Corporation |
R2-2008413 |
Summary of [AT111-e][013][NR16] RRC Misc I |
Ericsson |
R2-2008414 |
Summary of [AT111-e][014][NR16] RRC Misc II |
Ericsson |
R2-2008426 |
Summary of [AT111-e][013][NR16] RRC Misc I |
Ericsson |
R2-2008483 |
Miscellaneous correction regarding on demand SIB in CONNECTED |
Ericsson |
R2-2008484 |
Redundant procedural text of on demand SIB in CONNECTED |
Ericsson |
R2-2008616 |
Miscellaneous correction regarding on demand SIB in CONNECTED |
Ericsson |
R2-2008617 |
Redundant procedural text of on demand SIB in CONNECTED |
Ericsson |
R2-2008636 |
Correction on field description of mrdc-SecondaryCellGroup in NR-DC |
Samsung Electronics |
R2-2008686 |
Correction on field description of mrdc-SecondaryCellGroup in NR-DC |
Samsung Electronics |
6.1.2 |
Feature Lists and UE capabilities |
|
R2-2006508 |
LS on updated Rel-16 NR parameter lists (R1-2005051; contact: Qualcomm) |
RAN1 |
R2-2006510 |
LS on updated Rel-16 RAN1 UE features lists for NR (R1-2005096; contact: NTT DOCOMO, AT&T) |
RAN1 |
R2-2006511 |
LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#101-e (R1-2005109; contact: NTT DOCOMO, AT&T) |
RAN1 |
R2-2006526 |
LS on introducing UE capability for power class for NR band in MR-DC combination (RP-201392; contact: Huawei) |
RAN |
R2-2006558 |
Introduce capabilities on Async NR-DC and cell-grouping configuration |
Qualcomm Incorporated |
R2-2006646 |
Correction on RLF Report for Inter-RAT MRO NR |
CATT |
R2-2006880 |
Clarification on the support of beamSwitchTiming values of 224 and 336 |
Lenovo, Motorola Mobility, Qualcomm Incorporated, Ericsson |
R2-2006881 |
Correction on the support of beamSwitchTiming values of 224 and 336 |
Lenovo, Motorola Mobility, Qualcomm Incorporated, Ericsson |
R2-2006882 |
Correction on the support of beamSwitchTiming values of 224 and 336 |
Lenovo, Motorola Mobility, Qualcomm Incorporated, Ericsson |
R2-2006893 |
CR to 38.331 on UE autonomous gap related capabilities |
ZTE Corporation, Sanechips, Ericsson, Nokia, Nokia Shanghai Bell, MediaTek Inc, Qualcomm Incorporated, Intel Corporation |
R2-2006894 |
CR to 38.306 on UE autonomous gap related capabilities |
ZTE Corporation, Sanechips, Ericsson, Nokia, Nokia Shanghai Bell, MediaTek Inc, Qualcomm Incorporated, Intel Corporation |
R2-2006936 |
Report of email discussion [Post109bis-e][082] UE Capabilties |
Intel Corporation, NTT DoCoMo |
R2-2006937 |
Rel-16 UE capabilities based on RAN1 and RAN4 feature lists and RAN2 corrections |
Intel Corporation, NTT DoCoMo |
R2-2006938 |
Rel-16 UE capabilities based on RAN1 and RAN4 feature lists and RAN2 corrections |
Intel Corporation, NTT DoCoMo |
R2-2006940 |
Reply LS on Rel-16 UE feature lists |
Intel Corporation |
R2-2007112 |
Discussion on UE capability for power class for NR band in MR-DC combination |
Apple |
R2-2007113 |
UE capability for power class for NR band in MR-DC combination |
Apple |
R2-2007114 |
UE capability for power class for NR band in MR-DC combination |
Apple |
R2-2007498 |
Capability signalling for limited TRS bandwidth for 10 MHz bandwidth with 15 kHz SCS |
Nokia, Nokia Shanghai Bell |
R2-2007499 |
Capability signalling for limited TRS bandwidth for 10 MHz bandwidth with 15 kHz SCS |
Nokia, Nokia Shanghai Bell |
R2-2007505 |
Correction on beamSwitchTiming values of 224 and 336 |
vivo |
R2-2007506 |
Correction on beamSwitchTiming values of 224 and 336 |
vivo |
R2-2007605 |
UE capabilities for NR-DC |
Ericsson |
R2-2007801 |
Introduction of new PowerClass for NR part in MR-DC |
Huawei, HiSilicon |
R2-2007802 |
Introduction of new PowerClass for NR part in MR-DC |
Huawei, HiSilicon |
R2-2007803 |
Support of flexible TRS bandwidth sizes |
Huawei, HiSilicon |
R2-2007804 |
Support of flexible TRS bandwidth sizes |
Huawei, HiSilicon |
R2-2007946 |
Correction on non-SFN-sync NR-DC support |
Huawei, HiSilicon |
R2-2007997 |
Early Release Support of Features in NR |
CMCC,ZTE,Huawei,CATT |
R2-2007998 |
CR for Early Implementation in NR |
CMCC,ZTE,Huawei,CATT |
R2-2008064 |
Discussion on early measurement capabilities |
MediaTek Inc. |
R2-2008077 |
Introduction of new PowerClass for NR part in MR-DC |
Huawei, HiSilicon, CMCC |
R2-2008078 |
Introduction of new PowerClass for NR part in MR-DC |
Huawei, HiSilicon, CMCC |
R2-2008084 |
Early Release Support of Features in NR |
CMCC,ZTE,Huawei,CATT,Ericsson |
R2-2008085 |
CR for Early Implementation in NR |
CMCC,ZTE,Huawei,CATT,Ericsson |
R2-2008089 |
Support of new newly defined TRS bandwidth sizes |
Huawei, HiSilicon, Ericsson, Vodafone |
R2-2008090 |
Support of new newly defined TRS bandwidth sizes |
Huawei, HiSilicon, Ericsson, Vodafone |
R2-2008103 |
CR for Early Implementation in NR |
CMCC, ZTE, Huawei, CATT, Ericsson |
R2-2008118 |
Rel-16 UE capabilities based on RAN1 and RAN4 feature lists and RAN2 corrections |
Intel Corporation, NTT DoCoMo |
R2-2008119 |
Rel-16 UE capabilities based on RAN1 and RAN4 feature lists and RAN2 corrections |
Intel Corporation, NTT DoCoMo |
R2-2008316 |
Correction on beamSwitchTiming values of 224 and 336 |
vivo |
R2-2008317 |
Correction on beamSwitchTiming values of 224 and 336 |
vivo |
R2-2008318 |
LS to RAN1 on beamSwitchTiming |
RAN2 |
R2-2008395 |
Reply LS on Rel-16 UE feature lists |
RAN2 |
R2-2008406 |
[AT111-e][016][NR16] UE cap TRS bandwidth (Nokia) |
Nokia |
R2-2008407 |
[AT111-e][020][NR16] UE cap RF FR2 (Nokia) |
Nokia |
R2-2008422 |
Summary of ? [AT111-e][021][NR16] UE cap NR-DC |
Qualcomm |
R2-2008424 |
Report of email discussion AT111-e][015][NR16] UE cap Main Part1 |
Intel Corporation, NTT DoCoMo |
R2-2008433 |
ummary of offline 018 UE cap MR-DC Power Class |
Huawei, HiSilicon |
R2-2008434 |
Support of new newly defined TRS bandwidth sizes |
Huawei, HiSilicon, Ericsson, Vodafone |
R2-2008435 |
Support of new newly defined TRS bandwidth sizes |
Huawei, HiSilicon, Ericsson, Vodafone |
R2-2008438 |
Report from email discussion [AT111-e][017][NR16] UE cap Beam Switch Timing |
Lenovo |
R2-2008441 |
LS on updated Rel-16 RAN1 UE features lists for NR (R1-2007136; contact: NTT DOCOMO, AT&T) |
RAN1 |
R2-2008445 |
Summary of offline 019 UE cap UL TX switching |
China Telecom |
R2-2008459 |
Reply LS on Rel-16 RAN1 UE feature lists for 5G V2X service (R4-2011681; contact: LGE) |
RAN4 |
R2-2008539 |
Report of email discussion [AT111-e][015][NR16] UE cap Main - Class 3 issues |
Intel Corporation, NTT DOCOMO, INC. (Email discussion rapporteur) |
R2-2008579 |
Summary of Offline discussion#021: UE cap NR-DC (Qualcomm) |
Qualcomm |
R2-2008580 |
[AT111-e][020][NR16] UE cap RF FR2 (Nokia) |
Nokia |
R2-2008618 |
Summary of Offline discussion#021: UE cap NR-DC (Qualcomm) |
Qualcomm |
R2-2008637 |
Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 |
Intel Corporation, NTT DoCoMo, INC. |
R2-2008638 |
Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 corrections |
Intel Corporation, NTT DOCMO, INC. |
R2-2008641 |
Miscellaneous corrections on UL Tx switching |
China Telecom, ZTE Corporation, Sanechips, vivo, Apple, Huawei, HiSilicon, OPPO |
R2-2008642 |
Miscellaneous corrections on UL Tx switching |
China Telecom, Huawei, HiSilicon, OPPO, ZTE Corporation, Apple, vivo |
R2-2008646 |
CR for Early Implementation in NR |
CMCC, ZTE, Huawei, CATT, Ericsson, Samsung Electronics Co., Ltd , MediaTek Inc., British Telecom, Nokia, Nokia Shanghai Bell, Intel, vivo |
R2-2008660 |
NR-DC UE capabilities |
Qualcomm Incorporated |
R2-2008661 |
NR-DC UE capabilities |
Qualcomm Incorporated |
R2-2008662 |
LS on cell-grouping UE capability for synchronous NR-DC |
RAN2 |
R2-2008669 |
Miscellaneous corrections on UL Tx switching |
China Telecom, ZTE Corporation, Sanechips, vivo, Apple, Huawei, HiSilicon, OPPO, CATT |
R2-2008670 |
Miscellaneous corrections on UL Tx switching |
China Telecom, Huawei, HiSilicon, OPPO, ZTE Corporation, Sanechips, Apple, vivo, CATT |
R2-2008687 |
CR for Early Implementation in NR |
CMCC, ZTE, Huawei, CATT, Ericsson, Samsung Electronics Co., Ltd , MediaTek Inc., British Telecom, Nokia, Nokia Shanghai Bell, Intel, vivo |
R2-2008689 |
Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 |
Intel Corporation, NTT DoCoMo, INC. |
6.1.3 |
Other |
|
R2-2006659 |
Miscellaneous corrections |
Samsung |
R2-2006716 |
Handling of early implementable features in NR |
Intel Corporation |
R2-2007020 |
Clarification on the presence of the field si-RequestConfigSUL |
Fujitsu |
R2-2007061 |
Stopping ongoing Random Access procedure |
LG Electronics Inc. |
R2-2007077 |
Corrections to on demand SI acquisition in RRC_CONNECTED |
Samsung Electronics Co., Ltd |
R2-2007641 |
ASN.1 corrections to maintain backwards compatibility |
Ericsson, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
R2-2007642 |
Remaining ASN.1 review issues |
Ericsson |
R2-2007713 |
Alignment of SR clause |
Ericsson, Samsung |
R2-2007717 |
Miscellaneous corrections |
Samsung |
R2-2007963 |
Miscellaneous corrections (Rapporteur) |
Qualcomm Incorporated |
R2-2008080 |
Clarification on the extended capability of NGEN-DC |
vivo |
R2-2008081 |
Clarification on the extended capability of NGEN-DC |
vivo |
R2-2008082 |
Clarification on the extended capability of NGEN-DC |
vivo |
R2-2008102 |
Early Release Support of Features in NR |
CMCC, ZTE, Huawei, CATT, Ericsson |
R2-2008108 |
Guidelines for RRC changes at RAN2#111e |
Ericsson |
R2-2008417 |
Summary report of [AT111-e][023][NR16] NGEN-DC capability |
vivo |
R2-2008420 |
38321 CR Corrections on stopping ongoing Random Access procedure |
LG Electronics Inc. |
R2-2008449 |
Report of [AT111-e][024][NR16] MAC Misc Corrections (Samsung) |
Samsung |
R2-2008450 |
Miscellaneous corrections |
Samsung, LG Electronics, Sharp, Ericsson, vivo |
R2-2008466 |
Miscellaneous corrections (Rapporteur) |
Qualcomm Incorporated |
R2-2008601 |
Clarification on the extended capability of NGEN-DC |
vivo |
R2-2008603 |
ASN.1 corrections to maintain backwards compatibility |
Ericsson, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
R2-2008604 |
Remaining ASN.1 review issues |
Ericsson |
R2-2008627 |
Summary for Early Implementation |
CMCC |
R2-2008628 |
CR for Early Implementation |
CMCC |
R2-2008682 |
Clarification on the extended capability of NGEN-DC |
vivo |
6.2.1 |
General and Stage-2 Corrections |
|
R2-2006504 |
LS on IAB updates to 38.300 (R1-2004872; contact: Qualcomm) |
RAN1 |
R2-2006517 |
LS on IAB F1-C traffic transfer for NSA IAB (R3-204165; contact: Nokia) |
RAN3 |
R2-2006520 |
LS on multiple UL BH mapping for F1-C (R3-204345; contact: Huawei) |
RAN3 |
R2-2006963 |
Correction to 38300 for IAB |
Qualcomm Incorporated |
R2-2007315 |
Miscellaneous Corrections on IAB in 38.300 |
ZTE, Sanechips |
R2-2007374 |
CR to 38.300 on BH RLC channel |
ZTE, Sanechips |
R2-2007509 |
IAB-MT capability signalling clarification |
Nokia, Nokia Shanghai Bell |
R2-2007535 |
Corrections to cell selection for IAB in NSA |
Samsung Electronics Romania |
R2-2007536 |
Correction to cell selection for IAB SA |
Samsung Electronics Romania |
R2-2007539 |
Corrections to capability signaling for IAB-MT |
Samsung Electronics Romania |
R2-2007545 |
Corrections to BH RLF in IAB |
Samsung Electronics Romania |
R2-2007965 |
Miscellaneous correction for TS 37.340 for IAB |
Huawei, HiSilicon |
R2-2008363 |
Summary of corrections to 38300 for IAB |
Qualcomm |
R2-2008440 |
[AT111-e][026][IAB] Summary of Stage-2 Corrections |
Qualcomm (Rapporteur) |
R2-2008444 |
LS to RAN2 on IAB-MT feature list (R4-2012563; contact: Qualcomm) |
RAN4 |
R2-2008545 |
CR to 38.300 on Integrated Access and Backhaul for NR |
Qualcomm (Rapporteur) |
R2-2008546 |
Miscellaneous corrections to 38.300 for IAB |
Qualcomm (Rapporteur) |
R2-2008645 |
Miscellaneous correction for TS 37.340 for IAB |
Huawei, HiSilicon, Qualcomm |
6.2.2 |
BAP Corrections |
|
R2-2007296 |
Packet handling after receiving default ID configuration in RRC |
LG Electronics Inc. |
R2-2007316 |
Corrections on IAB-DU IP address allocation in 38.340 |
ZTE, Sanechips |
R2-2007317 |
Corrections on IAB flow control in 38.340 |
ZTE, Sanechips |
R2-2007483 |
BAP routing configuration clarification |
Nokia, Nokia Shanghai Bell |
R2-2007484 |
Default configuration usage corrections in BAP |
Nokia, Nokia Shanghai Bell |
R2-2007966 |
Miscellaneous corrections to 38.340 for IAB |
Huawei, HiSilicon |
R2-2007967 |
Corrections on flow control BAP control PDU |
Huawei, HiSilicon |
R2-2008115 |
Summary of 6.2.2 for BAP corrections |
Huawei, HiSilicon |
R2-2008498 |
Summary of [AT111-e][027][IAB] BAP Corrections |
Huawei, HiSilicon |
R2-2008499 |
Miscellaneous corrections to 38.340 for IAB |
Huawei, HiSilicon |
6.2.3 |
User plane Corrections |
|
R2-2007199 |
IAB MAC - miscellaneous corrections and clarifications |
Samsung Electronics GmbH |
R2-2007318 |
Corrections on pre-BSR in 38.321 |
ZTE, Sanechips |
R2-2007319 |
Miscellaneous Corrections on IAB in 38.321 |
ZTE, Sanechips |
R2-2007320 |
CR to 38.321 on Guard Symbols MAC CE |
ZTE, Sanechips |
R2-2007728 |
RACH stop for SR triggered by Pre-emptive BSR |
ASUSTeK |
R2-2007968 |
Correction on Guard Symbols MAC CE |
Huawei, HiSilicon |
R2-2007969 |
Correction on RA cancellation for Pre-emptive BSR |
Huawei, HiSilicon |
R2-2008439 |
Outstanding issues for IAB MAC |
Samsung |
R2-2008502 |
IAB MAC - miscellaneous corrections and clarifications |
Samsung Electronics GmbH |
R2-2008624 |
IAB MAC - miscellaneous corrections and clarifications |
Samsung |
R2-2008685 |
IAB MAC - miscellaneous corrections and clarifications |
Samsung |
6.2.4 |
RRC Corrections |
|
R2-2007162 |
Corrections of RLF cause Signalling procedure |
vivo |
R2-2007321 |
Support of soft resource availability indication for paired spectrum |
ZTE, Sanechips |
R2-2007322 |
CR to 38.331 on support of soft resource availability indication for paired spectrum |
ZTE, Sanechips |
R2-2007323 |
Corrections on IAB-DU IP address allocation in 38.331 |
ZTE, Sanechips |
R2-2007324 |
Miscellaneous Corrections on IAB in 38.331 |
ZTE, Sanechips |
R2-2007325 |
CR to 36.331 on F1-C traffic over LTE |
ZTE, Sanechips |
R2-2007507 |
Corrections to iab-support indicator in NSA |
Samsung Electronics Romania |
R2-2007520 |
Corrections to iab-support indicator in SA |
Samsung Electronics Romania |
R2-2007522 |
Correction to intra-frequency reselection for IAB in NSA |
Samsung Electronics Romania |
R2-2007524 |
Corrections to intra-frequency reselection for IAB in SA |
Samsung Electronics Romania |
R2-2007534 |
Editorial corrections in BAP configuration |
Samsung Electronics Romania |
R2-2007538 |
Corrections to MCGFailureInformation procedure |
Samsung Electronics Romania |
R2-2007543 |
Corrections to ip address configuration for IAB |
Samsung Electronics Romania |
R2-2007546 |
Corrections to ULInformationTransferMRDC |
Samsung Electronics Romania |
R2-2007970 |
Miscellaneous corrections for TS 38.331 for IAB |
Huawei, HiSilicon |
R2-2007971 |
Correction on BAP operation during RRC re-establishment |
Huawei, HiSilicon |
R2-2007972 |
Corrections on F1-C transfer path |
Huawei, HiSilicon |
R2-2007973 |
Correction on the bh-rlfRecoveryFailure for IAB-MT |
Huawei, HiSilicon |
R2-2007974 |
Corrections on default BH RLC channel |
Huawei, HiSilicon |
R2-2007975 |
Correction on the value range of BH-LogicalChannelIdentity-Ext |
Huawei, HiSilicon |
R2-2007976 |
Correction on cellReservedForOperatorUse |
Huawei, HiSilicon |
R2-2007977 |
Correction on SearchSpace configuration for IAB |
Huawei, HiSilicon |
R2-2007978 |
Corrections on the IAB-MT TDD resource configuration |
Huawei, HiSilicon |
R2-2007979 |
Correction of on the IP address requesting in EN-DC |
Huawei, HiSilicon |
R2-2008088 |
Clean-up of misaligned requirements between procedure and field description |
LG Electronics France |
R2-2008394 |
Summary of IAB RRC Corrections |
Ericsson |
R2-2008503 |
Corrections on F1-C transfer path |
Huawei, HiSilicon |
R2-2008504 |
Correction on the value range of BH-LogicalChannelIdentity-Ext |
Huawei, HiSilicon |
R2-2008505 |
Correction on SearchSpace configuration for IAB |
Huawei, HiSilicon |
R2-2008506 |
Corrections on the BH RLF failure for IAB to TS 36.331 |
Huawei, HiSilicon, Ericsson |
R2-2008516 |
Corrections of RLF cause Signalling procedure |
vivo |
R2-2008521 |
CR to 36.331 on F1-C traffic over LTE |
ZTE, Sanechips |
R2-2008572 |
Summary of [AT111-e][029][IAB] RRC Corrections |
Ericsson |
R2-2008573 |
Miscellaneous IAB Corrections |
Ericsson |
R2-2008574 |
Miscellaneous IAB Corrections |
Ericsson |
6.2.5 |
UE capabilities |
|
R2-2006959 |
Remaining details of UE capabilities for IAB |
AT&T |
R2-2007508 |
Update to IAB-MT capabilities |
Nokia, Nokia Shanghai Bell |
R2-2007980 |
Correction on IAB-MT capability for TS 38.331 |
Huawei, HiSilicon |
R2-2007981 |
Correction on IAB-MT capability for TS 38.306 |
Huawei, HiSilicon |
R2-2008105 |
Summary of IAB UE capabilities under AI 6.2.5 |
Nokia (Summary Rapporteur) |
R2-2008460 |
Update to IAB-MT capabilities |
Nokia, Nokia Shanghai Bell |
R2-2008461 |
Update to IAB-MT capabilities |
Nokia, Nokia Shanghai Bell |
R2-2008567 |
Update to IAB-MT capabilities |
Nokia, Nokia Shanghai Bell |
R2-2008598 |
Summary of [AT111-e][030][IAB] UE capabilities (Nokia) |
Nokia, Nokia Shanghai Bell |
R2-2008634 |
Update to IAB-MT capabilities |
Nokia, Nokia Shanghai Bell |
6.2.6 |
Other Corrections |
|
R2-2007982 |
Miscellaneous corrections for TS 38.304 for IAB |
Huawei, HiSilicon |
R2-2007983 |
Miscellaneous corrections for TS 36.304 for IAB |
Huawei, HiSilicon |
6.3.1 |
General and Stage-2 Corrections |
|
R2-2006503 |
LS to RAN2 on clarification of RVID for the first transmission for CG-PUSCH (R1-2003074; contact: Qualcomm) |
RAN1 |
R2-2006507 |
LS to RAN2 on initial BWP for NR-U (R1-2004998; contact: Ericsson) |
RAN1 |
R2-2007450 |
Clarification on the CAPC selection for MSG3 and MSGA PUSCH |
ZTE Corporation, Sanechips |
R2-2008028 |
Miscellaneous corrections for NR-U (Rapporteur) |
Qualcomm Incorporated |
R2-2008396 |
LS on UE behavior for P/SP-CSI-RS reception in NR-U (R1-2006195; source: MediaTek) |
RAN1 |
R2-2008448 |
Report of [AT111-e][002][NR15] NR MAC corrections (Samsung) |
Samsung |
R2-2008452 |
Correction of CAPC for NR-U |
Nokia (Rapporteur) |
R2-2008475 |
Offline 504 on NR-U in 38.300 |
Nokia (Rapporteur) |
R2-2008600 |
LS on CAPC |
Nokia |
R2-2008671 |
LS on CAPC |
RAN2 |
R2-2008674 |
Correction of CAPC for NR-U |
Nokia (Rapporteur) |
R2-2008690 |
LS on CAPC |
RAN2 |
6.3.2 |
User plane |
|
R2-2006549 |
Remaining Issues on Stopping the Ongoing RA Procedure due to a Pending SR in NR-U |
vivo |
R2-2006658 |
Clarification on operations in a bundle of UL grants |
Samsung |
R2-2007169 |
Corrections on CG operation for NR-U |
Nokia, Nokia Shanghai Bell |
R2-2007188 |
Correction to LBT SR cancellation |
Nokia, Nokia Shanghai Bell |
R2-2007453 |
Clarifications in MAC for NR-U |
ZTE Corporation, Sanechips |
R2-2007548 |
Clarification on the transmission of LBT failure MAC CE on SCells |
Google Inc. |
R2-2007729 |
Further consideration on LBT failure cancellation regarding BWP switching |
ASUSTeK |
R2-2007817 |
Correction on 2-stepRA resource selection with semi-static channel access |
Huawei, HiSilicon |
R2-2007818 |
Correction on prority of SR for consistent LBT failure |
Huawei, HiSilicon |
R2-2007819 |
Correction on configured grant occasion detemination |
Huawei, HiSilicon |
R2-2007880 |
Review of CG timers |
LG Electronics UK |
R2-2007883 |
NR-U revision |
LG Electronics UK |
R2-2007892 |
The operation of drx-RetransmissionTimerUL |
ASUSTeK |
R2-2008371 |
Report of [AT111e][505][NR-U] CR to 38.321 (Nokia) |
Nokia, Nokia Shanghai Bell |
R2-2008372 |
Corrections for NR-U |
Nokia, Nokia Shanghai Bell, ASUSTek, LG, Huawei, ZTE |
R2-2008650 |
Corrections for NR operating with shared spectrum channel access |
Nokia, Nokia Shanghai Bell, ASUSTek, Ericsson, LG, Huawei, ZTE |
6.3.3 |
Control plane |
|
R2-2007066 |
searchSpaceSwitchingGroup handling |
Nokia, Nokia Shanghai Bell |
R2-2007067 |
Guardbands corrections |
Nokia, Nokia Shanghai Bell |
R2-2007451 |
RRC corrections for NR-U |
ZTE Corporation, Sanechips |
R2-2007452 |
RRC clarficiations for NR-U |
ZTE Corporation, Sanechips |
R2-2007596 |
Remaining RRC issues |
Ericsson |
R2-2007597 |
NR-U features in 38.306 |
Ericsson |
R2-2007621 |
Correction regarding placement of cell specific SSB QCL information in CLI MO |
Samsung Telecommunications |
R2-2007730 |
Corrections on configuredGrantTimer |
ASUSTeK |
R2-2007820 |
Correction on ServingCellConfig |
Huawei, HiSilicon |
R2-2007821 |
Correction on ssb-SubcarrierOffset in MIB |
Huawei, HiSilicon |
R2-2007822 |
Correction on RACH Configuration |
Huawei, HiSilicon, Ericsson |
R2-2007823 |
Correction on ControlResourceSet |
Huawei, HiSilicon |
R2-2007824 |
Correction on RSSI and CO measurement |
Huawei, HiSilicon |
R2-2008054 |
Clarification on pusch-TimeDomainResourceAllocationList |
Samsung |
R2-2008065 |
Correction to the search space switching timer |
vivo |
R2-2008382 |
RRC clarficiations for NR-U |
ZTE Corporation, Sanechips |
R2-2008383 |
Correction regarding placement of cell specific SSB QCL information |
Samsung |
R2-2008387 |
RRC clarficiations for NR-U |
ZTE Corporation, Sanechips |
R2-2008389 |
RRC clarficiations for NR-U |
ZTE Corporation, Sanechips |
R2-2008393 |
Remaining RRC issues |
Ericsson |
R2-2008402 |
Correction regarding placement of cell specific SSB QCL information in CLI MO |
Samsung Telecommunications |
R2-2008467 |
Miscellaneous corrections for NR-U |
Qualcomm (Rapporteur), Asustek, Ericsson, Huawei, Nokia, Samsung, Vivo, ZTE |
R2-2008468 |
Report of [AT111e][506][NR-U] CR to 38.331 |
Qualcomm Incorporated |
R2-2008629 |
Miscellaneous corrections for NR-U |
Qualcomm (Rapporteur), Asustek, Ericsson, Huawei, Nokia, Samsung, Vivo, ZTE |
6.4.1 |
General and Stage-2 corrections |
|
R2-2007307 |
Miscellaneous corrections to 38.321 |
Nokia, Nokia Shanghai Bell |
R2-2007868 |
Stage-2 corrections on 38.300 |
vivo |
R2-2007920 |
Correction for NR SL communication |
Samsung Electronics |
6.4.2 |
Control plane corrections |
|
R2-2006598 |
Left issues on cross-RAT control of sidelink (38.331) |
OPPO, Samsung |
R2-2006599 |
Left issues on cross-RAT control of sidelink (36.331) |
OPPO, Samsung |
R2-2006614 |
Correction on the names of ueAssistanceInformationNR and UEAssistanceInformation |
CATT |
R2-2006620 |
Correction to TS 38.304 |
CATT |
R2-2006621 |
Correction on the SL QoS in TS 38.331 |
CATT |
R2-2006622 |
Discussion on the Value Range of ul-PrioritizationThres and sl-PrioritizationThres |
CATT |
R2-2006744 |
Corrections on 38.331 CR for NR V2X cross RAT configuration |
ZTE Corporation, Sanechips |
R2-2006745 |
CR on TS 38.331 for miscellaneous issues for NR V2X |
ZTE Corporation, Sanechips |
R2-2006875 |
Correction to sidelink communication |
Google Inc. |
R2-2006876 |
Correction to NR sidelink related information reporting |
Google Inc. |
R2-2006914 |
Need for cross-RAT acknowledgement in V2X reconfigurations |
MediaTek Inc. |
R2-2007074 |
Corrections discarding segments of SIB 12 |
Samsung Electronics Co., Ltd |
R2-2007075 |
Corrections to discarding segments of SIB 28 |
Samsung Electronics Co., Ltd |
R2-2007079 |
Corrections to V2X SIB acquisition |
Samsung Electronics Co., Ltd |
R2-2007095 |
Correction on Stored Sidelink Measurement Configuration |
Apple |
R2-2007096 |
Correction on Cross-RAT OtherConfig |
Apple, InterDigital Inc. |
R2-2007193 |
Addition of field description for single TX resource pool sidelink mode 1 to 38.331 for V2X |
Nokia, Nokia Shanghai Bell |
R2-2007198 |
Correction to TX resource pool sidelink mode 1 and 2 in 38.331 for V2X |
Nokia, Nokia Shanghai Bell |
R2-2007206 |
CR on TS 38.331 for remaining RB issues for NR V2X resource pool |
ZTE Corporation, Sanechips |
R2-2007227 |
Some remaining aspects regarding V2X IRAT RAT signalling |
Samsung Telecommunications, OPPO |
R2-2007228 |
Corrections regarding NR CBR (V2X IRAT) measurements |
Samsung Telecommunications, OPPO |
R2-2007235 |
On the number of TX resource pools for sidelink mode 1 |
Nokia, Nokia Shanghai Bell |
R2-2007239 |
Clarification on security for NR SL communication in TS 38.331 |
Huawei, HiSilicon |
R2-2007242 |
Correction on cross-RAT V2X functionality in TS 36.331 |
Huawei, HiSilicon |
R2-2007243 |
Correction on cross-RAT V2X functionality in TS 38.331 |
Huawei, HiSilicon |
R2-2007244 |
CR on security for NR SL communication in TS 38.331 |
Huawei, HiSilicon |
R2-2007245 |
CR on SidelinkUEInformationNR reporting in TS 38.331 |
Huawei, HiSilicon |
R2-2007263 |
Further RRC Issue on the presence "Cond CBR" sl-MaxTxPower in SL-PSSCH-TxParameters |
Nokia, Nokia Shanghai Bell |
R2-2007280 |
Correction to default value of field sl-X-Overhead |
Ericsson |
R2-2007281 |
Correction to sidelink fields in the inter-node RRC messages |
Ericsson |
R2-2007282 |
Correction to the setting of empty SL RRC messages |
Ericsson |
R2-2007283 |
Correction on LTE V2X configuration in the RRCReconfiguration |
Ericsson |
R2-2007284 |
Sending of RRC reconfiguration complete message in SL crossRAT |
Ericsson |
R2-2007285 |
Sending of RRC reconfiguration complete message in SL crossRAT |
Ericsson |
R2-2007286 |
Sending of RRC reconfiguration complete message in SL crossRAT |
Ericsson |
R2-2007298 |
Addition of the missing anchor carrier pre-configuration for NR SL communication in TS 36.331 |
Huawei, HiSilicon |
R2-2007299 |
CR on SL power control parameters in TS 38.331 |
Huawei, HiSilicon |
R2-2007383 |
Corrections to Sidelink process |
Nokia, Nokia Shanghai Bell |
R2-2007395 |
Correction to transmission of MasterInformationBlockSidelink |
Ericsson |
R2-2007731 |
Clarification on RRC reconfiguration failure for SL DRB addition |
ASUSTeK |
R2-2007732 |
Clarification on SL DRB release |
ASUSTeK |
R2-2007786 |
Clarification on RRC signaling/procedure for acknowledging cross-RAT SL configuration in current RRC Spec - Inexistence of “Issue 1” discussed by RAN plenary |
Huawei, CATT, Apple, ZTE Corporation, LG Electronics Inc., Intel Corporation, HiSilicon |
R2-2007848 |
Miscellaneous corrections on V2X for TS 38.331 |
Samsung |
R2-2007852 |
Miscellaneous corrections on TS 38.331 |
Huawei, HiSilicon |
R2-2007853 |
Correction on the periodicity value for configured sidelink type 1 |
Huawei, HiSilicon |
R2-2007854 |
Correction on measurement quantity configuration for SL RSRP reporting |
Huawei, HiSilicon |
R2-2007855 |
Correction on missing SDAP header configuration in PC5 RRC signaling |
Huawei, HiSilicon |
R2-2007856 |
Correction on optionality of ueCapabilityRequestFilterSidelink |
Huawei, HiSilicon |
R2-2007857 |
Correction on the procedure for PC5 RRC release |
Huawei, HiSilicon |
R2-2007866 |
Sidelink synchronization ID |
Qualcomm Finland RFFE Oy |
R2-2007869 |
38.331 CR on cross-RAT signalling for NR V2X |
vivo |
R2-2007870 |
36.331 CR on cross-RAT signalling for LTE V2X |
vivo |
R2-2007871 |
Miscellaneous corrections to 38.331 on SL operation |
vivo |
R2-2007872 |
Remaining issue on SL/UL prioritization |
vivo |
R2-2007876 |
38.304 Correction on cell (re)selection for sidelink UE |
vivo |
R2-2007877 |
36.304 Correction on cell (re)selection for sidelink UE |
vivo |
R2-2007881 |
Sidelink priority threshold |
Qualcomm Finland RFFE Oy |
R2-2007886 |
Sidelink synchronization ID |
Qualcomm Finland RFFE Oy, Ericsson, Apple, Kyocera, ZTE, CATT, InterDigital, Lenovo, Motorola Mobility |
R2-2007908 |
Miscellaneous corrections on TS 36.331 |
Huawei, Hisilicon |
R2-2007917 |
Addition of the missing resource pool ID associated with each configured sidelink grant type1 |
Huawei, Hisilicon |
R2-2007921 |
Correction for sidelink priority threshold (alternative 1) |
Samsung Electronics |
R2-2007922 |
Correction for sidelink priority threshold (alternative 2) |
Samsung Electronics |
R2-2007923 |
Correction to SL-ConfigDedicatedNR and SL-ScheduledConfig |
Samsung Electronics |
R2-2008037 |
Corrections on synchronisation, timing offset signalling and Uplink/Downlink TDD configuration |
LG Electronics France |
R2-2008050 |
Corrections on sidelinkUEInformation transmission and SL mode 1 TX pool configuration |
LG Electronics France |
R2-2008099 |
Clarification on RRC signaling/procedure for acknowledging cross-RAT SL configuration in current RRC Spec - Inexistence of “Issue 1” discussed by RAN plenary |
Huawei, CATT, Apple, ZTE Corporation, LG Electronics Inc., Intel Corporation, Lenovo, Motorola Mobility, HiSilicon |
R2-2008117 |
Summary of AI 6.4.2 — CP corrections for 5G V2X with NR SL |
Huawei, HiSilicon |
R2-2008321 |
Miscellaneous corrections on TS 38.331 |
Huawei, HiSilicon |
R2-2008322 |
Miscellaneous corrections on TS 36.331 |
Huawei, HiSilicon |
R2-2008323 |
Correction on RRC parameters for 5G V2X with NR sidelink |
Huawei, HiSilicon |
R2-2008324 |
Addition of the missing NR anchor carrier pre-configuration for V2X SL communication in TS 36.331 |
Huawei, HiSilicon |
R2-2008325 |
Adding notes for joint success and failure in crossRAT SL |
Ericsson, MediaTek Inc., OPPO, Samsung |
R2-2008326 |
Adding a note for joint success and failure in crossRAT SL |
Ericsson, MediaTek Inc., OPPO, Samsung |
R2-2008327 |
Correction on cross-RAT V2X functionality in TS 38.331 |
Huawei, HiSilicon |
R2-2008328 |
Correction on cross-RAT V2X functionality in TS 36.331 |
Huawei, HiSilicon |
R2-2008347 |
Corrections on RAN1 related clarifications |
ZTE Corporation, Sanechips |
R2-2008351 |
Sidelink synchronization ID |
Qualcomm Finland RFFE Oy, Ericsson, Apple, Kyocera, ZTE, CATT, InterDigital, Lenovo, Motorola Mobility |
R2-2008356 |
Correction to TS 38.304 |
CATT |
R2-2008357 |
36.304 Correction on cell (re)selection for sidelink UE |
vivo |
R2-2008403 |
CR to 38.331 on SLSS ID |
Qualcomm, Ericsson, Apple, Kyocera, ZTE, CATT, InterDigital, Lenovo, Motorola Mobility |
R2-2008559 |
Correction on cross-RAT V2X functionality in TS 36.331 |
Huawei, HiSilicon |
R2-2008560 |
Correction on RRC parameters for 5G V2X with NR sidelink |
Huawei, HiSilicon |
R2-2008581 |
CR to 38.331 on SLSS ID |
Qualcomm, Ericsson, Apple, Kyocera, ZTE, CATT, InterDigital, Lenovo, Motorola Mobility, Nokia, Intel Corporation |
6.4.3 |
User plane corrections |
|
R2-2006561 |
Corrections to UE behavior upon SL BWP deactivation |
vivo |
R2-2006568 |
Correction on resource re-selection trigger |
vivo |
R2-2006585 |
CR for left issues of NR V2X on MAC |
OPPO |
R2-2006613 |
Consideration on the Priority of UL MAC CE |
CATT |
R2-2006615 |
Correction on the sidelink transmission information |
CATT |
R2-2006616 |
Corrections on TS 37.324 |
CATT |
R2-2006617 |
Correction on BSR procedure |
CATT |
R2-2006618 |
Correction on the SR cancellation condition |
CATT |
R2-2006619 |
Correction on the LCP procedure |
CATT |
R2-2006623 |
Remaining Issue of the UL/SL Prioritization |
CATT |
R2-2006704 |
Corrections to 5G V2X with NR Sidelink |
LG Electronics France |
R2-2006706 |
Corrections to 5G V2X with NR Sidelink |
LG Electronics France |
R2-2006739 |
Discussion on remaining issues of NR UL-SL prioritisation |
ZTE Corporation, Sanechips |
R2-2006740 |
CR on TS 38.321 for UL-SL prioritization issues for NR V2X |
ZTE Corporation, Sanechips |
R2-2006741 |
CR on TS 36.321 for UL-SL prioritization issues for NR V2X |
ZTE Corporation, Sanechips |
R2-2006742 |
CR on TS 38.321 for issues related to NR V2X LCP |
ZTE Corporation, Sanechips |
R2-2006743 |
CR on TS 38.321 for miscellaneous issues for NR V2X resource selection |
ZTE Corporation, Sanechips |
R2-2006762 |
Discussion on setting of range parameter in SCI |
InterDigital, Apple, Ericsson, Qualcomm, Nokia, Mediatek, Fraunhofer HHI, Fraunhofer IIS, Convida Wireless |
R2-2006763 |
Corrections for setting of range parameter in SCI |
InterDigital, Apple, Ericsson, Qualcomm, Nokia, Mediatek, Fraunhofer HHI, Fraunhofer IIS, Convida Wireless |
R2-2006764 |
Correction for Determining Need for Next Transmission for DG with HARQ Disabled |
InterDigital, Apple |
R2-2006765 |
Miscellaneous Corrections on HARQ Process Operation |
InterDigital, Apple |
R2-2006766 |
Corrections to HARQ-Based RLF at TX UE |
InterDigital, Apple |
R2-2006768 |
Discussion on prioritization between UL and SL |
OPPO |
R2-2006769 |
Discussion on resource and HARQ process id of configured grant |
OPPO |
R2-2006776 |
Corrections to data inactivity monitoring considering SL logical channels |
Samsung Electronics Co., Ltd |
R2-2006818 |
Discussion on HARQ related issues |
ZTE Corporation, Sanechips |
R2-2006819 |
CR on TS 38.321 for HARQ issues for NR V2X |
ZTE Corporation, Sanechips |
R2-2006820 |
CR on TS 38.321 for remaining HARQ issues for NR V2X |
ZTE Corporation, Sanechips |
R2-2006823 |
CR on TS 38.321 for Sidelink grant issues for NR V2X |
ZTE Corporation, Sanehcips |
R2-2006877 |
Corrections to SL-BSR truncation |
Ericsson, Qualcomm Incorporated |
R2-2007021 |
Discussion on NR-V2X MAC left issues |
Fujitsu |
R2-2007090 |
Correction on SL-SCH MAC header |
Apple, InterDigital Inc. |
R2-2007091 |
Correction on UL/SL Prioritization procedures |
Apple, InterDigital Inc. |
R2-2007092 |
Correction on Sidelink resource selection procedures |
Apple |
R2-2007093 |
Correction on Sidelink LCP procedure |
Apple |
R2-2007094 |
Correction on Sidelink HARQ Process |
Apple, InterDigital Inc. |
R2-2007241 |
Correction on ciphering and integrity functions for NR SL communication in TS 38.323 |
Huawei, HiSilicon |
R2-2007247 |
RLF in absence of data |
Lenovo, Motorola Mobility |
R2-2007287 |
Prioritization between UL Uu and SL when priorities are not configured |
Ericsson |
R2-2007288 |
Prioritization between UL Uu and SL when priorities are not configured |
Ericsson |
R2-2007289 |
Prioritization between UL Uu and SL when priorities are not configured |
Ericsson |
R2-2007297 |
Corrections to Sidelink HARQ entity |
Nokia, Nokia Shanghai Bell |
R2-2007500 |
Corrections on LCP procedure for NR V2X |
Lenovo (Beijing) Ltd |
R2-2007640 |
Sidelink type 2 groupcast reception upon member ID |
Nokia, Nokia Shanghai Bell |
R2-2007648 |
Correction to Sidelink mode 2 resource selection for retransmission |
Nokia, Nokia Shanghai Bell |
R2-2007733 |
Clarification on ciphering for Direct Security Mode Command message |
ASUSTeK |
R2-2007734 |
Clarification on PC5 QoS flow remapping |
ASUSTeK |
R2-2007735 |
MAC Corrections for NR V2X |
ASUSTek |
R2-2007787 |
Clarification on NR UL and SL transmission prioritization with pre-configured priority thresholds - Inexistence of “Issue 2” discussed by RAN plenary |
Huawei, HiSilicon |
R2-2007858 |
Correction on the HARQ-based Sidelink RLF detection |
Huawei, HiSilicon |
R2-2007873 |
Support RLC Re-establishment |
vivo |
R2-2007874 |
Corrections to SL-BSR triggered by retxBSR-Timer expiry |
vivo |
R2-2007875 |
Miscellaneous corrections for MAC |
vivo |
R2-2007878 |
Corrections to the scope of PDU format for V2X |
vivo |
R2-2007879 |
RACH for CSI reporting |
vivo |
R2-2007900 |
Resource reservation period |
Qualcomm Finland RFFE Oy |
R2-2007907 |
Miscellaneous corrections to 38.321 for V2X |
Huawei, Hisilicon |
R2-2007909 |
Correction on the MAC reset |
Huawei, Hisilicon |
R2-2007910 |
Correction on HARQ feedback on PUCCH |
Huawei, Hisilicon |
R2-2007911 |
Correction on MAC subheaders for SL-SCH |
Huawei, Hisilicon |
R2-2007912 |
Correction on sidelink BSR |
Huawei, Hisilicon |
R2-2007913 |
Correction on soft buffer handling for RX UE |
Huawei, Hisilicon |
R2-2007914 |
Correction on NR UL and LTE SL prioritization |
Huawei, Hisilicon |
R2-2007915 |
Correction on logical channel prioritization |
Huawei, Hisilicon |
R2-2007916 |
Correction on resource (re)selection |
Huawei, Hisilicon |
R2-2007918 |
Discussion on sidelink grant handling |
Huawei, Hisilicon |
R2-2007919 |
Discussion on the calculation of SL CG occasion |
Huawei, Hisilicon |
R2-2007924 |
Correction to C-DRX for NR SL communication |
Samsung Electronics |
R2-2007925 |
Correction to Destination Index in SL-BSR MAC CE |
Samsung Electronics |
R2-2007926 |
Correction to LCP procedures |
Samsung Electronics |
R2-2007927 |
Correction to LTE Uu control for NR SL communication |
Samsung Electronics |
R2-2007928 |
Correction to RNTI for V2X SL communication |
Samsung Electronics |
R2-2007929 |
Correction to sidelink specific MAC reset |
Samsung Electronics |
R2-2007930 |
Correction to MAC subheader for SL-SCH |
Samsung Electronics |
R2-2007931 |
Correction to PSFCH reception |
Samsung Electronics |
R2-2007932 |
Correction to SL BSR trigger event |
Samsung Electronics |
R2-2007933 |
Correction to TX resource pool selection procedures |
Samsung Electronics |
R2-2007934 |
Correction to TX resource selection check procedures |
Samsung Electronics |
R2-2007935 |
Miscelleneous corrections to NR SL communication |
Samsung Electronics |
R2-2007964 |
Discussion on groupcast HARQ feedback without location |
Huawei, Hisilicon |
R2-2008029 |
CR to 38.321 on SL HARQ ACK transmission |
LG Electronics France |
R2-2008110 |
Corrections to 5G V2X with NR Sidelink |
LG Electronics |
R2-2008111 |
Corrections to 5G V2X with NR Sidelink |
LG Electronics |
R2-2008112 |
Report of RAN2#111-e_V2X MAC |
LG Electronics (Rapporteur) |
R2-2008113 |
Summary of MAC open issues for NR sidelink |
LG Electronics (Rapporteur) |
R2-2008329 |
Summary on the offline discussion on the sidelink configured grant handling |
Huawei, HiSilicon |
R2-2008330 |
Corrections to 5G V2X with NR Sidelink |
LG Electronics |
R2-2008332 |
Summary of [AT111-e][705][V2X] 38.321/36.321 Miscellaneous corrections (LG) |
LG Electronics Inc |
R2-2008333 |
Corrections to Prioritization for 5G V2X with NR Sidelink |
LG Electronics Inc. |
R2-2008334 |
Corrections to 5G V2X with NR Sidelink |
LG Electronics |
R2-2008335 |
Clarification on UL and SL priority thresholds |
vivo |
R2-2008336 |
Discussion of [AT111-e][706][V2X] Corrections for prioritization (LG for discussion and MAC CR, Vivo for RRC CR) |
LG Electronics Inc. (Rapporteur) |
R2-2008337 |
Corrections for CSI reporting |
CATT |
R2-2008338 |
[AT111-e][707][V2X] Corrections for CSI Reporting (CATT) |
CATT |
R2-2008348 |
Corrections to SL-BSR truncation |
Ericsson, Huawei |
R2-2008353 |
Correction on resource (re)selection |
Huawei, HiSilicon |
R2-2008354 |
Draft LS to RAN1 on sidelink configured grant handling |
Huawei |
R2-2008355 |
Draft LS to RAN1 on sidelink configured grant handling |
Huawei |
R2-2008358 |
38.323 corrections on Sidelink |
CATT, Huawei, HiSilicon, ASUSTeK, vivo |
R2-2008359 |
37.324 corrections on Sidelink |
CATT, ASUSTeK |
R2-2008528 |
Summary of [AT111-e][711][V2X] Corrections on BSR |
Ericsson |
R2-2008583 |
Correction on the calculation of CG occasion |
Huawei, HiSilicon |
R2-2008584 |
Summary of [POST111-e][705][V2X] Proposal 2-1 and 2-2 (Huawei) |
Huawei (Rapporteur) |
R2-2008585 |
LS on RAN2 agreements and RAN1 related issues |
RAN2 |
R2-2008586 |
LS to RAN1 on sidelink configured grant handling |
RAN2 |
R2-2008587 |
Correction on the calculation of CG occasion |
Huawei, HiSilicon |
R2-2008630 |
Corrections to 5G V2X with NR Sidelink |
LG Electronics |
R2-2008631 |
Corrections to 5G V2X with NR Sidelink |
LG Electronics |
R2-2008632 |
Corrections to prioritization for 5G V2X with NR Sidelink |
LG Electronics |
R2-2008644 |
Correction on the calculation of CG occasion |
Huawei, HiSilicon |
R2-2008678 |
Corrections to SL-BSR truncation |
Ericsson, Huawei |
6.4.4 |
UE capabilities |
|
R2-2006584 |
[Draft] LS on V2X UE capability |
OPPO |
R2-2006586 |
Summary of [Post110-e][707][V2X] V2X UE capabilities (OPPO) |
OPPO |
R2-2006587 |
Draft 38.331 CR for V2X UE capability (for RAN2 capability) |
OPPO |
R2-2006588 |
Draft 38.306 CR for V2X UE capability (for RAN2 capability) |
OPPO |
R2-2006589 |
Draft 38.331 CR for V2X UE capability (for RAN1/RAN4 capability) |
OPPO |
R2-2006590 |
Draft 38.306 CR for V2X UE capability (for RAN1/RAN4 capability) |
OPPO |
R2-2006591 |
36.331 CR for V2X UE capability |
OPPO |
R2-2006592 |
36.306 CR for V2X UE capability |
OPPO |
R2-2007240 |
Correction on band filtering function in capability exchange in PC5 RRC |
Huawei, HiSilicon |
R2-2007252 |
Reducing the signalling of peer UE capability transfer in unicast sidelink |
Nokia, Nokia Shanghai Bell |
R2-2008339 |
[Draft] LS on UE capability |
OPPO |
R2-2008341 |
Draft 38.331 CR for V2X UE capability (for RAN2 capability) |
OPPO |
R2-2008342 |
Draft 38.331 CR for V2X UE capability (for RAN1/RAN4 capability) |
OPPO |
R2-2008343 |
Draft 38.306 CR for V2X UE capability (for RAN2 capability) |
OPPO |
R2-2008344 |
Draft 38.306 CR for V2X UE capability (for RAN1/RAN4 capability) |
OPPO |
R2-2008345 |
CR for V2X UE capability |
OPPO |
R2-2008346 |
CR for V2X UE capability |
OPPO |
R2-2008349 |
LS on UE capability |
RAN2 |
R2-2008350 |
LS on UE capability for V2X |
RAN2 |
R2-2008362 |
Draft 38.331 CR for V2X UE capability (for RAN2 capability) |
OPPO |
R2-2008446 |
Report of [AT111-e][012][NR15] Idle mode |
Qualcomm Incorporated |
R2-2008497 |
LS on UE capability |
RAN2 |
6.5.1 |
General and Stage-2 corrections |
|
R2-2006505 |
Reply LS on Intra-UE Prioritization R1-2004899; contact: LGE) |
RAN1 |
R2-2006509 |
LS on Intra-UE Prioritization for data with different priorities (R1-2005078; contact: vivo) |
RAN1 |
R2-2006518 |
Response LS on Network Coordination for UL PDCP Duplication (R3-204168; contact: Nokia) |
RAN3 |
R2-2006637 |
Clarify Packet Duplication in 38.300 |
CATT |
R2-2006917 |
LCH Mapping Restriction issues with DC+CA PDCP Duplication |
Nokia, Nokia Shanghai Bell |
R2-2006918 |
Stage-2 CR for clarifications of DC+CA PDCP Duplication |
Nokia, Nokia Shanghai Bell |
R2-2007138 |
Consideration on LCH mapping restriction when duplication deactivation |
OPPO |
R2-2007387 |
Clarification on definition of DC+CA duplication |
Huawei, HiSilicon |
R2-2008537 |
Summary of e-mail discussion: [AT111-e][043][IIOT] Stage 2 |
Nokia, Nokia Shanghai Bell |
R2-2008538 |
Stage-2 CR for clarifications of Rel-16 PDCP Duplication |
Nokia, Nokia Shanghai Bell |
6.5.2 |
RRC Corrections |
|
R2-2006710 |
Discussion about the misalignment of the unit of SPS periodicities |
Huawei, HiSilicon |
R2-2006711 |
Correction on the unit of extended SPS periodicities |
Huawei, HiSilicon |
R2-2006727 |
Correction on field description of ethernetHeaderCompression |
Huawei, HiSilicon |
R2-2006828 |
Correction on field description of configuredGrantConfig and SPS-Config |
Huawei, HiSilicon |
R2-2006888 |
Miscellaneous RRC corrections for NR IIoT |
Ericsson, Samsung |
R2-2007142 |
A clarification of pdcp-Duplication field |
OPPO |
R2-2007151 |
38.331 Clarification on pdcp-Duplication IE |
vivo |
R2-2007388 |
Correction on configuration of PDCP duplication |
Huawei, HiSilicon |
R2-2008492 |
Summary on [AT111e][031][IIOT] RRC Corrections (Ericsson) |
Ericsson |
R2-2008610 |
Miscellaneous corrections for NR IIoT |
Ericsson (Rapporteur), Samsung, OPPO, vivo, Huawei, HiSilicon |
6.5.3 |
MAC Corrections |
|
R2-2006600 |
Clarification on Duplication RLC Activation/Deactivation MAC CE |
vivo |
R2-2006698 |
Correction of IIoT in 38.321 |
CATT |
R2-2006712 |
Correction on the calculation of HARQ Process ID for SPS |
Huawei, HiSilicon |
R2-2006726 |
Correction on the term of configuredGrantConfigList |
Huawei, HiSilicon |
R2-2006863 |
CR to PUSCH duration comparision with MSGA transmission |
Fujitsu |
R2-2006919 |
MAC CR for clarifications of DC+CA PDCP Duplication |
Nokia, Nokia Shanghai Bell |
R2-2007106 |
Clarifications on intra UE prioritization - capability and configuration |
Apple |
R2-2007107 |
On conflicting scenarios for LCH and PHY prioritization |
Apple |
R2-2007108 |
Modifications for LCH and PHY prioritization scenarios |
Apple |
R2-2007127 |
Handing of inconsistency between PHY-based and LCH-based prioritization configuration |
China Telecommunications |
R2-2007131 |
Corrections for intra-UE prioritization |
Ericsson |
R2-2007132 |
Corrections for Multiple Entry Configured Grant Confirmation MAC CE |
Ericsson, Samsung |
R2-2007137 |
Consideration on intra-UE prioritization with same PHY priority |
OPPO |
R2-2007147 |
UE autonomous retransmission considering the processing time |
vivo,Samsung, Lenovo |
R2-2007389 |
Correction on resource overlapping with grants addressed to T-C-RNTI |
Huawei, HiSilicon |
R2-2007390 |
Correction on construction of Multiple Entry Configured Grant Confirmation MAC CE |
Huawei, HiSilicon |
R2-2007527 |
CR on 38.321 for SPS resources and HARQ process ID calculation |
ZTE Corporation, Sanechips |
R2-2007530 |
Considieration on the lack of time to process the autonomous transmission |
ZTE Corporation, Sanechips |
R2-2007531 |
Considerations on the Duplicagtion RLC ativation/deactivation MAC CE |
ZTE Corporation, Sanechips |
R2-2008055 |
Miscellaneous corrections for IIOT MAC |
Samsung |
R2-2008057 |
Issue on independent configuration of intra-UE prioritization |
Samsung |
R2-2008058 |
Priority of Uplink Grant |
Samsung |
R2-2008397 |
Report of Offline 033: IIOT MAC Corrections II |
Samsung |
R2-2008496 |
Miscellaneous corrections for IIOT MAC |
Samsung |
R2-2008517 |
Summary of Offline Discussions on Intra UE prioritization |
Apple |
R2-2008518 |
[DRAFT] LS on Intra UE Prioritization Scenario |
Ericsson |
R2-2008529 |
Correction on the calculation of HARQ Process ID for SPS |
Huawei, HiSilicon |
R2-2008535 |
Correction on the term of configuredGrantConfigList |
Huawei, HiSilicon, CATT, Ericsson |
R2-2008542 |
Report of Offline 032: MAC Support For PDCP duplication |
ZTE Corporation, Sanechips |
R2-2008597 |
Summary of Offline Discussions on Intra UE prioritization |
Apple |
R2-2008599 |
LS on Intra UE Prioritization Scenario |
RAN2 |
R2-2008651 |
Miscellaneous Corrections for intra-UE prioritization |
Ericsson |
R2-2008663 |
Modifications for LCH and PHY Prioritization Scenarios |
Apple |
6.5.4 |
PDCP Corrections |
|
R2-2006728 |
Correction on receive opearation when both EHC and out-of-order delivery are configured for a DRB |
Huawei, HiSilicon |
R2-2008479 |
Correction on receive opearation when both EHC and out-of-order delivery are configured for a DRB |
Huawei, HiSilicon |
R2-2008536 |
Correction on receive operation when both EHC and out-of-order delivery are configured for a DRB |
Huawei, HiSilicon |
6.5.4.1 |
Duplication |
|
R2-2007133 |
Corrections on differentiating CA and DC duplication |
Ericsson |
R2-2007891 |
38300 CR Corrections on Packet Duplication |
LG Electronics Inc. |
R2-2008056 |
Cell Restriction Lifting in CA+DC Duplication |
Samsung |
6.5.4.2 |
Ethernet Header Compression |
|
R2-2006725 |
Discussion about the decompression failure caused by context overwriting in EHC |
Huawei, HiSilicon |
R2-2008030 |
EHC decompression failure at LTE PDCP re-establishment |
Samsung |
R2-2008034 |
CR on LTE PDCP re-establishment when t-Reordering is used |
Samsung |
R2-2008035 |
LTE EHC configuration for split and LWA DRBs |
Samsung |
R2-2008036 |
LTE EHC configuration for split and LWA DRBs |
Samsung |
R2-2008044 |
CR on LTE EHC configuration |
Samsung |
R2-2008478 |
[AT111-e][034][IIOT] EHC Corrections |
Samsung |
R2-2008480 |
CR on LTE EHC configuration |
Samsung |
R2-2008541 |
CR on LTE PDCP re-establishment when t-Reordering is used |
Samsung |
R2-2008681 |
CR on LTE EHC configuration |
Samsung |
6.5.5 |
Other |
|
R2-2006920 |
Remaining issues on Intra-UE prioritization |
Nokia, Nokia Shanghai Bell |
R2-2007148 |
SFN tracking for the reference time |
vivo |
R2-2007149 |
Discussion on CA duplication and DC+CA duplication |
vivo |
R2-2007150 |
38.300 Clarification on relationship between PDCP duplication and SCell activation/deactivation |
vivo |
6.6.1 |
General and Stage 2 corrections |
|
R2-2006522 |
Reply LS on Aperiodic SRS (R3-204379; contact: Intel) |
RAN3 |
R2-2006523 |
LS on mapping of PosSIB(s) to Area(s) (R3-204380; contact: Huawei) |
RAN3 |
R2-2006841 |
Signalling sequence for UL SRS Configuration |
Ericsson |
R2-2007630 |
Correction to SUPL support for NR positioning methods |
Qualcomm Incorporated |
R2-2007828 |
DraftCR to Stage-2 for gNB and LMF information transfer |
Huawei, HiSilicon |
R2-2007829 |
Text proposal on stage2 spec for aperiodic SRS |
Huawei, HiSilicon |
R2-2007830 |
TP for POSITIONING INFORMATION REQUEST |
Huawei, HiSilicon |
R2-2007831 |
Miscellaneous correction to stage2 specification |
Huawei, HiSilicon |
R2-2008098 |
Summary of 6.6.1 |
CATT |
R2-2008493 |
Correction on Stage-2 for gNB and LMF information transfer |
Huawei, HiSilicon |
R2-2008494 |
Miscellaneous correction to stage2 spec |
Huawei, HiSilicon |
R2-2008495 |
Signalling sequence correction for UL SRS Configuration |
Ericsson |
R2-2008514 |
LS on the NOTE in architecture figure in TS 38.305 (R3-205719; contact: Intel) |
RAN3 |
R2-2008614 |
[AT111-e][609][POS] Checking of R2-2007831, R2-2007828, and R2-2006841 (Huawei) |
Huawei, HiSilicon |
6.6.2 |
RRC corrections |
|
R2-2006544 |
Remaining issues on measurement gap for NR positioning |
vivo |
R2-2006664 |
Correction on 38.331 to capture agreements of area scope for posSIB validity |
CATT |
R2-2006844 |
Addition of extension marker for positioning SI broadcast status |
Ericsson |
R2-2006926 |
Measurement gaps for PRS-based measurements |
Ericsson |
R2-2006942 |
Minor corrections and update for RRC Positioning |
Ericsson |
R2-2007078 |
Corrections to handing posSIB-MappingInfo in received SIB1 |
Samsung Electronics Co., Ltd |
R2-2007547 |
Corrections to unused field nr-CarrierFreq and misalignment between LPP and RRC |
Samsung Electronics Romania |
R2-2007559 |
Introuduction of UE Capabilitues for support of measurement gaps for PRS-based measurements |
Ericsson |
R2-2007581 |
Summary of the AI 6.6.2 for positioning RRC correction |
Huawei, HiSilicon |
R2-2007832 |
Introduction of PRS mesurement gap |
Huawei, HiSilicon |
R2-2007837 |
Correction on PRS mesurement gap capability |
Huawei, HiSilicon |
R2-2008258 |
Minor corrections and update for RRC Positioning |
Ericsson |
R2-2008271 |
[AT111-e][610][POS] RRC miscellaneous CR (Ericsson) |
Ericsson |
R2-2008273 |
Corrections to handing posSIB-MappingInfo in SIB1 |
Samsung Electronics |
R2-2008647 |
Introduction of PRS measurement gap |
Huawei, HiSilicon, Ericsson |
R2-2008648 |
Correction on PRS measurement gap capability |
Huawei, HiSilicon, Ericsson |
R2-2008688 |
Correction on PRS measurement gap capability |
Huawei, HiSilicon, Ericsson |
6.6.3 |
LPP corrections |
|
R2-2006543 |
Correction of DL-PRS-NumSymbols |
vivo |
R2-2006546 |
Discussion on remaining issues on LPP |
vivo |
R2-2006663 |
Correction on 37.355 to capture agreements of area scope for posSIB validity |
CATT |
R2-2006847 |
Need of reference TRP in the TRP-LocationInfo IE for UE-based assistance data distribution efficiency |
Ericsson |
R2-2006949 |
Handling on RAN1 positioning related capabilities |
Intel Corporation |
R2-2006950 |
Capture RAN1 positioning related capabilities |
Intel Corporation |
R2-2007632 |
Addition of missing SRS for Positioning capabilities |
Qualcomm Incorporated |
R2-2007634 |
Assistance data sharing and priority for measurements |
Qualcomm Incorporated |
R2-2007635 |
Addition of missing padding rule for initial counter c0 |
Qualcomm Incorporated |
R2-2007833 |
Correction of the SRS capability in LPP |
Huawei, HiSilicon |
R2-2007834 |
Correction on SignalMeasurementInformation |
Huawei, HiSilicon |
R2-2007835 |
Correction on ProvideAssistantData |
Huawei, HiSilicon |
R2-2007836 |
Correction on PRS configuration |
Huawei, HiSilicon |
R2-2007941 |
Correction to NR-SSB-Config |
ZTE Corporation, Sanechips |
R2-2008120 |
Summary of LPP corrections agenda item 6.6.3 |
Qualcomm Incorporated |
R2-2008260 |
LPP miscellaneous corrections |
Qualcomm Incorporated |
R2-2008268 |
Summary of email discussion [AT111-e][611][POS] LPP miscellaneous CR |
Qualcomm Incorporated |
6.6.4 |
MAC corrections |
|
R2-2006545 |
Discussion on SRS for positioning during the DRX inactive period |
vivo |
6.7.1 |
General and Stage-2 Corrections |
|
R2-2007016 |
Minor Correction for CPC configuration related procedure |
CATT, ZTE Corporation |
R2-2007266 |
SCG handling at DAPS HO |
Ericsson, ZTE Corporation (Rapporteur), Sanechips |
R2-2007267 |
SCG handling at DAPS HO |
Ericsson |
R2-2007359 |
Various corrections to NR Mobility enhancements description |
Nokia, Nokia Shanghai Bell |
R2-2007542 |
Correction for editorial structure of CPC section |
Samsung Electronics Romania |
R2-2007698 |
Clarification on SCells and SCG release at DAPS HO |
ZTE Corporation, Sanechips, Ericsson |
R2-2007699 |
Clarification on SCells and SCG release at DAPS HO |
ZTE Corporation, Sanechips, Ericsson |
R2-2008132 |
Report from [AT111-e][202][MOB] LTE and NR mobility Stage-2 corrections (Nokia) |
Nokia, Nokia Shanghai Bell |
6.7.2 |
Conditional handover related corrections |
|
R2-2006869 |
Correction to conditional configurations |
Google Inc. |
R2-2007018 |
Minor Correction for Mobility Further Enhancement |
CATT |
R2-2007229 |
Internode signalling upon reconfiguration of source Pcell |
Samsung Telecommunications |
R2-2007230 |
Clarifications regarding CHO |
Samsung Telecommunications |
R2-2007361 |
Corrections to Conditional Reconfiguration triggering |
Nokia, Nokia Shanghai Bell |
R2-2007502 |
Corrections to number of candidate cell in CHO |
Samsung Electronics Romania |
R2-2007593 |
Correction of Need Code for Mobility Enhancements |
Ericsson |
R2-2007594 |
Correction of description of CHO events for Mobility Enhancements |
Ericsson |
R2-2007663 |
Correction to update of CHO configuration |
Samsung |
R2-2007664 |
Corrections to Mobility Enahncements |
Samsung |
R2-2007700 |
Discussion on the cell selection triggered by CHO failure |
ZTE Corporation, Sanechips |
R2-2007701 |
Clarification on the cell selection triggered by CHO failure (Alt. 1) |
ZTE Corporation, Sanechips |
R2-2007702 |
Clarification on the cell selection triggered by CHO failure (Alt. 2) |
ZTE Corporation, Sanechips |
R2-2007703 |
Clarification on the cell selection triggered by CHO failure (Alt. 1) |
ZTE Corporation, Sanechips |
R2-2007704 |
Clarification on the cell selection triggered by CHO failure (Alt. 2) |
ZTE Corporation, Sanechips |
R2-2007705 |
Timer handling upon initiation of RRC re-establishment |
ZTE Corporation, Sanechips |
R2-2007706 |
Timer handling upon initiation of RRC re-establishment |
ZTE Corporation, Sanechips |
R2-2007718 |
UE assistance information transmission in CHO case |
SHARP Corporation |
R2-2007764 |
Correction on TS 38.331 for CHO |
Huawei, HiSilicon |
R2-2007765 |
Correction on TS 36.331 for CHO |
Huawei, HiSilicon |
R2-2007859 |
Correction on NR CHO |
OPPO |
R2-2008011 |
Discussion on physical cell id for CHO configurations |
Huawei, HiSilicon |
R2-2008133 |
Summary of discussion [203] [MOB] CHO and CPC corrections (Intel) |
Intel |
R2-2008168 |
Correction to conditional configurations |
Google Inc. |
R2-2008170 |
Timer handling upon initiation of RRC re-establishment |
ZTE Corporation, Sanechips |
R2-2008292 |
Correction of description of CHO events for Mobility Enhancements |
Ericsson |
R2-2008294 |
Timer handling upon initiation of RRC re-establishment |
ZTE Corporation, Sanechips |
R2-2008519 |
Correction on TS 36.331 for CHO |
Huawei, HiSilicon |
6.7.3 |
Conditional PSCell change for intra-SN corrections |
|
R2-2007360 |
Corrections to CPC with and without SRB3 involved |
Nokia, Nokia Shanghai Bell |
R2-2007592 |
Correction of field description for Mobility Enhancements |
Ericsson |
R2-2007595 |
Correction of signaling flow for CPC |
Ericsson |
R2-2007707 |
Discussion on the compliance check failure for CPC configuration after PCell change |
ZTE Corporation, Sanechips |
R2-2007708 |
Compliance check failure for CPC configuration |
ZTE Corporation, Sanechips |
R2-2007709 |
Compliance check failure for CPC configuration |
ZTE Corporation, Sanechips |
R2-2007766 |
Correction on TS 38.331 for CPC |
Huawei, HiSilicon |
R2-2007767 |
Correction on TS 36.331 for CPC |
Huawei, HiSilicon |
R2-2008172 |
Correction of signaling flow for CPC |
Ericsson |
R2-2008398 |
Discussion on the compliance check failure for CPC configuration after PCell change |
ZTE Corporation, Sanechips |
R2-2008399 |
Compliance check failure for CPC configuration |
ZTE Corporation, Sanechips |
R2-2008400 |
Compliance check failure for CPC configuration |
ZTE Corporation, Sanechips |
6.7.4 |
UE capabilities |
|
R2-2007454 |
Discussion on UE capabilities for NR DAPS |
Huawei, HiSilicon, Vivo, Mediatek Inc. |
R2-2007455 |
Discussion on per UE NR mobility capabilities |
Huawei, HiSilicon |
R2-2007457 |
Correction on TS 38.306 for DAPS |
Huawei, HiSilicon |
R2-2007591 |
Multi quantity event for CHO |
Ericsson |
R2-2007610 |
UE Capabilities for DAPS |
Ericsson |
R2-2007845 |
Miscellaneous corrections for Rel-16 UE capabilities |
Samsung |
R2-2007846 |
Miscellaneous corrections for Rel-16 UE capabilities |
Samsung |
R2-2007847 |
Miscellaneous corrections for Rel-16 UE capabilities |
Samsung |
R2-2008144 |
Report of [AT111-e][214][MOB] DAPS UE capability structure for LTE/NR mobility (Huawei) |
Huawei, HiSilicon |
R2-2008145 |
Correction on DAPS UE capability structure |
Huawei, HiSilicon, Ericsson |
R2-2008146 |
Correction on DAPS UE capability structure |
Huawei, HiSilicon, Ericsson |
R2-2008149 |
Reply LS on Rel-16 UE feature lists for NR DAPS |
RAN2 |
R2-2008555 |
Corrections on UE capabilities for NR_Mob_enh |
China Telecom |
R2-2008556 |
Corrections on UE capabilities for NR_Mob_enh |
China Telecom |
6.7.5 |
Other |
|
R2-2007017 |
Correction on Source Cell Group and Source SpCell |
CATT |
R2-2007482 |
RRC Re-establishment at RLF in target PCell during DAPS HO |
Ericsson |
R2-2007495 |
T312 handling during Mobility From NR |
Lenovo, Motorola Mobility |
R2-2007571 |
RLF in source cell during DAPS handover |
Ericsson |
R2-2008018 |
CR on drb-ContinueROHC for DAPS |
Samsung |
R2-2008135 |
[AT111-e][205][NR MOB] DAPS RLF and NR-specific corrections to Rel-16 mobility |
nnEricsson |
R2-2008558 |
CR on drb-ContinueROHC for DAPS |
Samsung |
6.8.1 |
General and Stage-2 Corrections |
|
R2-2006897 |
CR to 37.340 on SCG resume procedure |
ZTE Corporation, Sanechips |
R2-2007582 |
Misc corrections for Rel-16 DCCA |
Ericsson Inc. |
R2-2007583 |
Misc corrections for Rel-16 DCCA |
Ericsson Inc. |
R2-2007584 |
Misc corrections for Rel-16 DCCA |
Ericsson Inc. |
R2-2007585 |
Misc corrections for Rel-16 DCCA |
Ericsson Inc. |
R2-2007690 |
Correction on power coordination in NR-DC |
Huawei, HiSilicon |
R2-2007691 |
Correction on UL behaviours in the dormant BWP |
Huawei, HiSilicon |
R2-2008138 |
[AT111-e][208][DCCA] Corrections SCell dormancy (Nokia) |
Nokia, Nokia Shanghai Bell |
R2-2008151 |
[AT111-e][208][DCCA] Corrections SCell dormancy (Nokia) |
Nokia, Nokia Shanghai Bell |
R2-2008530 |
Correction on UL behaviours in the dormant BWP |
Huawei, HiSilicon |
R2-2008551 |
Misc corrections for Rel-16 DCCA |
Ericsson Inc. |
R2-2008552 |
Misc corrections for Rel-16 DCCA |
Ericsson Inc. |
R2-2008553 |
Misc corrections for Rel-16 DCCA |
Ericsson Inc. |
R2-2008554 |
Misc corrections for Rel-16 DCCA |
Ericsson Inc. |
R2-2008576 |
Reply LS on UL PC for NR-DC (R1-2007261; contact: Apple) |
RAN1 |
R2-2008619 |
Miscellaneous corrections for DCCA |
ZTE Corporation (Rapporteur) |
6.8.2 |
MAC Corrections |
|
R2-2006559 |
Discussion on how to avoid frequent and redundant PHR triggered by dormant BWP switch |
Qualcomm Incorporated |
R2-2006560 |
CR to 38.321 on introducing PHR prohibit timer for PHR triggered by dormant BWP switch |
Qualcomm Incorporated |
R2-2006679 |
Discussion on Scell reactivation in a dormant and non-dormant BWP |
SHARP Corporation |
R2-2006810 |
Clarifications on PHR triggers-R15 |
OPPO |
R2-2006811 |
Clarifications on PHR triggers-R16 |
OPPO |
R2-2006812 |
Discussion on frequent PHR trigger due to dormancy transition. |
OPPO |
R2-2007216 |
Redundant and frequent PHR reporting in NR |
vivo |
R2-2007217 |
correction on the UE behaviour on dormant state |
vivo |
R2-2007218 |
correction on the UE behaviour on dormant state |
vivo |
R2-2007219 |
correction on the UE behaviour on dormant BWP |
vivo |
R2-2007905 |
Discussion on the timing of scellDecativatedTimer for direct scell activation |
vivo |
R2-2007906 |
(Draft) LS on the timing of scellDecativatedTimer for direct scell activation |
vivo |
R2-2007947 |
Correction on PHR triggering upon BWP switching from dormant BWP to non-dormant BWP |
Huawei, HiSilicon |
R2-2008014 |
CR on the terminology of PHR trigger |
Samsung |
R2-2008180 |
Correction on dormant SCell |
Nokia, Nokia Shanghai Bell, Samsung |
6.8.3.1 |
Fast Scell activation |
|
R2-2007003 |
Correction on the Dormant BWP |
CATT |
R2-2007684 |
Correction on dormant BWP |
Huawei, HiSilicon |
6.8.3.2 |
Early measurement reporting |
|
R2-2007004 |
CR to 38.331 on involving all fields of early measurement report |
CATT |
R2-2007005 |
CR to 36.331 on involving all fields of early measurement report |
CATT |
R2-2007205 |
Correction on idle/inactive measurement after cell (re)selection |
Google Inc. |
R2-2007220 |
Correction on early measurement configuration during inter-RAT cell reselection |
vivo |
R2-2007622 |
Correction information structure of early measurement results for additional EUTRA frequencies |
Samsung Telecommunications |
R2-2007682 |
Correction on updating the measurement configuration and performing measurement in early measurement |
Huawei, HiSilicon |
R2-2007685 |
Correction on the descriptions of the two idlemodeMeasurementReq fields |
Huawei, HiSilicon |
R2-2007688 |
Summary of [Post110-e][080][DCCA] Early Measurements and Network Sharing |
Huawei |
R2-2008008 |
Corrections to the UE behavior upon reception of RRCSetup while T331 is running |
Samsung Electronics Co., Ltd |
R2-2008009 |
Corrections on the behaviours with cell (re-)selection while T331 is running |
Samsung Electronics Co., Ltd |
R2-2008010 |
Corrections on the UE behavior upon PLMN reselection while T331 is running |
Samsung Electronics Co., Ltd |
R2-2008139 |
[AT111-e][209][DCCA] Corrections to early measurement reporting |
Ericsson |
6.8.3.3 |
Other |
|
R2-2006780 |
Corrections to failure type for MCGFailureInformation and SCGFailureInformation |
Samsung Electronics Co., Ltd |
R2-2006813 |
Correction on sk-Counter-R15 |
OPPO |
R2-2006814 |
Correction on sk-Counter-R16 |
OPPO |
R2-2006815 |
Clarifications on concept of suspend XCG transmission |
OPPO |
R2-2006886 |
Add tdm-PatternConfig-r16 in the inter-node message |
Google Inc. |
R2-2007006 |
Correction on the Configuration of sCellState for 38.331 |
CATT |
R2-2007007 |
Correction on the Configuration of sCellState for 36.331 |
CATT |
R2-2007008 |
Correction on the Field Description for Field Using SetupRelease Structure |
CATT |
R2-2007221 |
Adding enableDefaultBeamForCSS for cross-carrier scheduling with different SCS |
vivo |
R2-2007277 |
Remaining issues on Toffset for NR-DC power control |
Ericsson |
R2-2007278 |
Remaining issues on Toffset for NR-DC power control |
Ericsson |
R2-2007279 |
Correction to field condition on refFR2ServCellAsyncCA |
Ericsson |
R2-2007578 |
Missing fields for Toffset coordination in INM |
Ericsson |
R2-2007680 |
Correction on HARQ ACK spatial bundling configurations for secondary PUCCH group |
Huawei, HiSilicon |
R2-2007681 |
Correction on storing SCG configuration in UE INACTIVE AS context |
Huawei, HiSilicon |
R2-2007683 |
Correction on SCG RLF detection while MCG is suspended |
Huawei, HiSilicon |
R2-2007686 |
Miscellaneous corrections for fast MCG link recovery |
Huawei, HiSilicon |
R2-2007687 |
Miscellaneous corrections for fast MCG link recovery |
Huawei, HiSilicon |
R2-2007882 |
Clarification on CA slot offset configuration |
MediaTek Inc. |
R2-2008140 |
[AT111-e][210][DCCA] Other DCCA Corrections |
Ericsson |
R2-2008150 |
Correction on HARQ ACK spatial bundling configurations for secondary PUCCH group |
Huawei, HiSilicon |
R2-2008177 |
Corrections to failure type for MCGFailureInformation and SCGFailureInformation |
Samsung Electronics Co., Ltd |
R2-2008365 |
Issue on SCell Slot Slit for Unaligned CA |
CMCC |
R2-2008366 |
Corrections on Unaligned CA |
CMCC |
R2-2008436 |
Correction on the Configuration of sCellState for 38.331 |
CATT |
R2-2008437 |
Correction on the Configuration of sCellState for 36.331 |
CATT |
R2-2008451 |
Adding enableDefaultBeamForCCS for cross-carrier scheduling with different SCS |
vivo |
R2-2008507 |
Correction on storing SCG configuration in UE INACTIVE AS context |
Huawei, HiSilicon |
R2-2008508 |
Add tdm-PatternConfig2 in the inter-node message |
Google Inc. |
R2-2008540 |
Correction on the Configuration of sCellState for 38.331 |
CATT |
R2-2008594 |
Missing fields for Toffset coordination in INM |
Ericsson |
R2-2008633 |
Corrections to failure type for MCGFailureInformation and SCGFailureInformation |
Samsung Electronics Co., Ltd |
6.8.4 |
Other |
|
R2-2006562 |
CR to 36.306 on UE capability of direct SCell activation |
Qualcomm Incorporated |
R2-2006563 |
CR to 36.331 on UE capability of direct SCell activation |
Qualcomm Incorporated |
6.9.2 |
User plane Corrections |
|
R2-2006684 |
Prioritization between DCP and RAR |
vivo |
R2-2006989 |
Correction on prioritization between DCP and RAR to C-RNTI |
CATT |
R2-2007259 |
RAR prioritization over DCP |
Ericsson, Nokia, Nokia Shanghai Bell |
R2-2007369 |
Remaining issues of DCP overlapping with RAR |
OPPO |
R2-2007391 |
Prioritization between DCP and RAR addressed to C-RNTI |
Samsung |
R2-2007528 |
CR on 38.321 for CSI and SRS in the case that DCP is configured |
ZTE Corporation, Sanechips |
R2-2007529 |
Considerations on the CSI and SRS in the case that DCP is configured |
ZTE Corporation, Sanechips |
R2-2008374 |
Correction on prioritization between DCP and RAR to C-RNTI |
CATT |
R2-2008379 |
Correction on prioritization between DCP and RAR to C-RNTI |
CATT |
R2-2008380 |
Correction on prioritization between DCP and RAR to C-RNTI for CFRA BFR |
CATT |
R2-2008384 |
Correction on prioritization between DCP and RAR to C-RNTI for CFRA BFR - Option 2 |
CATT |
6.9.3 |
Control plane Corrections |
|
R2-2006685 |
Discussion on how to restructure the RRM relaxation |
vivo, Samsung, LG Electronics Inc., MediaTek Inc., Panasonic |
R2-2006686 |
RRM relaxation for high priority frequency |
vivo, Samsung, ZTE, Intel, Panasonic |
R2-2006687 |
[Draft] LS to RAN4 on RRM measurement relaxation in power saving |
vivo |
R2-2006688 |
Value range for UAI in power saving |
vivo |
R2-2006988 |
Inter-node exchange of UAI for SCG during handover |
CATT |
R2-2007063 |
Correction to UE behavior for RRM measurement relaxation |
Samsung Electronics |
R2-2007232 |
Repetition of SCG related (power saving) assistance upon synchronous reconfiguration/ handover |
Samsung Telecommunications |
R2-2007367 |
RRM relaxation for higher priority frequency |
OPPO |
R2-2007368 |
CR for UE assistance information for releasePreference |
OPPO |
R2-2007576 |
Misc. corrections CR for 38.331 for Power Savings |
MediaTek Inc. |
R2-2007808 |
Correction for UAI transmission in NR-DC case |
Huawei, HiSilicon |
R2-2007809 |
Correction on condition of prohibit timer for power saving |
Huawei, HiSilicon |
R2-2007810 |
Correction on field description of preferredDRX-LongCycle |
Huawei, HiSilicon |
R2-2007811 |
Correction on field description of maxMIMO-Layers |
Huawei, HiSilicon |
R2-2007812 |
Correction on other configuration release for SCG (38.331) |
Huawei, HiSilicon |
R2-2007813 |
Correction on other configuration release for SCG (36.331) |
Huawei, HiSilicon |
R2-2007814 |
Corrections on clarificaiton of the cell group specific UE assistance information |
Huawei, HiSilicon |
R2-2007815 |
Discussion on preferredDRX-ShortCycleTimer |
Huawei, HiSilicon |
R2-2007904 |
Add UE assistance information in CG-ConfigInfo |
Google Inc. |
R2-2008129 |
Summary of Rel-16 power saving RRC issues |
MediaTek Inc. |
R2-2008364 |
Summary of Rel-16 power saving RRC issues |
CATT |
R2-2008373 |
Misc. corrections CR for 36.331 for Power Savings |
MediaTek Inc |
R2-2008375 |
Summary of offline discussion on restructuring for the RRM relaxation |
vivo |
R2-2008376 |
CR on 38.304 for UE Power saving in NR |
vivo |
R2-2008377 |
[AT111e][502][PowSav] RRC open issues |
MediaTek Inc. |
R2-2008378 |
Misc. corrections CR for 38.331 for Power Savings |
MediaTek Inc. |
R2-2008381 |
Misc. corrections CR for 38.331 for Power Savings |
MediaTek Inc., CATT, Huawei, HiSilicon, Google |
R2-2008385 |
Misc. corrections CR for 36.331 for Power Savings |
MediaTek Inc., CATT, Huawei, HiSilicon |
R2-2008568 |
CR for UE Power Saving in NR |
vivo |
R2-2008569 |
Summary of RRM relaxation behaviors |
vivo, CATT |
6.10.1 |
General and stage-2 corrections |
|
R2-2006515 |
limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT HO (R3-204115; contact: LGE) |
RAN3 |
R2-2006521 |
LS on propagation of user consent related information during Xn inter-PLMN handover (R3-204378; contact: Nokia) |
RAN3 |
R2-2006535 |
Reply LS to LS on removal of Management Based MDT Allowed IE for NR (S5-203410; contact: Ericsson) |
SA5 |
R2-2006816 |
Drafting Rules in subclause 15 on SON |
Nokia, Nokia Shanghai Bell |
R2-2007371 |
Correction on Accessibility measurements |
Samsung |
R2-2007427 |
Summary for 6.10.1 General and stage-2 corrections |
CMCC |
R2-2007512 |
Impact of SNPN on PLMN check for MDT |
Nokia, Nokia Shanghai Bell |
R2-2007671 |
Corrections in TS 37.320 |
Ericsson |
R2-2007750 |
Corrections on MDT stage-2 descriptions |
Huawei, HiSilicon |
R2-2007780 |
Mislleneous corrections to 37320 |
ZTE Corporation, Sanechips |
R2-2007781 |
Correction to 38306 on inter-RAT MRO feature |
ZTE Corporation, Sanechips |
R2-2007860 |
Corrections for TS37.320 |
CATT |
R2-2008282 |
Corrections to TS 37.320 |
CMCC, Nokia, Nokia Shanghai Bell |
R2-2008283 |
Summary of MDT stage-2 issues |
CMCC |
R2-2008289 |
Drafting Rules in subclause 15 on SON |
Nokia, Nokia Shanghai Bell |
6.10.2 |
TS 38.314 corrections |
|
R2-2007422 |
Discussion on introduction of per PLMN L2M |
CMCC |
R2-2007423 |
Introduction of per PLMN L2M |
CMCC |
R2-2007424 |
Typo correction for Packet Error Rate |
CMCC |
R2-2007425 |
Summary for 6.10.2 TS 38.314 corrections |
CMCC |
R2-2007513 |
Unclarity on L2 measurements applicability to IAB |
Nokia, Nokia Shanghai Bell |
R2-2007514 |
Delay measurement for IAB |
Nokia, Nokia Shanghai Bell |
R2-2007669 |
On M4 measurement related clarification |
Ericsson |
R2-2007670 |
On EUTRA related L2 measurements for EN-DC |
Ericsson |
R2-2007751 |
Discussion on average Uu delay measurement for L2M |
Huawei, HiSilicon |
R2-2007752 |
Discussion on D1 measurement for L2M |
Huawei, HiSilicon |
R2-2008547 |
Report of [AT111-e][802] 38.314 corrections |
CMCC |
R2-2008548 |
Correction for L2M to capture agreements from [AT111-e][802] offline discussion |
CMCC |
6.10.3 |
RRC corrections |
|
R2-2006644 |
Correction about Including Re-connection Cell ID in RLF Report |
CATT |
R2-2006645 |
Correction about Including Re-connection Cell ID in RLF Report |
CATT |
R2-2006647 |
Correction on RLF Report for Inter-RAT MRO EUTRA |
CATT |
R2-2006648 |
Clarification on RLF Report for Inter-RAT MRO |
CATT |
R2-2006649 |
Clarifications for MeasResult2NR and MeasResult2EUTRA Relevant IEs |
CATT |
R2-2006650 |
Add TA Information in CEF Report when T319 Expire |
CATT |
R2-2007214 |
Correction on cross-RAT RLF report |
Google Inc. |
R2-2007224 |
Clarification on MDT regarding reporting of WLAN and BT information |
Samsung Telecommunications |
R2-2007225 |
Clarification on MDT regarding area configuration and target frequencies |
Samsung Telecommunications |
R2-2007226 |
Specification of target frequencies for measurement logging |
Samsung Telecommunications |
R2-2007372 |
Corrections on ConnEstFailReport |
Samsung |
R2-2007373 |
Correction on RA-Report |
Samsung |
R2-2007382 |
Logging PLMN Info in VarConnEstFailReport |
Samsung |
R2-2007384 |
Moving IE InterFreqTargetList out of IE AreaConfiguration |
Samsung |
R2-2007385 |
Avoiding Duplication of Location Info upon SCG Failure |
Samsung |
R2-2007386 |
How to Determine Whether a Cell is Part of the Area Indicated by AreaConfiguration |
Samsung |
R2-2007510 |
Correction on RA-Report release |
Nokia, Nokia Shanghai Bell |
R2-2007511 |
Correction to RLF cause determination for backhaul failure |
Nokia, Nokia Shanghai Bell |
R2-2007657 |
On the need of SCell indication in the RA-report |
Ericsson |
R2-2007668 |
On the inclusion of reconnectCellId |
Ericsson |
R2-2007753 |
Discussion on user consent |
Huawei, HiSilicon |
R2-2007754 |
Editorial corrections on MDT and SON in NR |
Huawei, HiSilicon |
R2-2007755 |
Correction on MDT and SON configurations for MR-DC |
Huawei, HiSilicon |
R2-2007756 |
Correction on logged MDT |
Huawei, HiSilicon |
R2-2007757 |
Correction on the release of obtainCommonLocation |
Huawei, HiSilicon |
R2-2007758 |
Correction on Inter-RAT SON for 38.331 |
Huawei, HiSilicon |
R2-2007759 |
Correction on Inter-RAT SON for 36.331 |
Huawei, HiSilicon |
R2-2007760 |
Correction on clearing VarRLF-Report regarding T316 |
Huawei, HiSilicon |
R2-2007761 |
Summary on 6.10.3 RRC Corrections |
Huawei |
R2-2007776 |
Correction on GNSS location information reporting in MDT |
ZTE Corporation, Sanechips |
R2-2007777 |
Correction to 38331 on logged MDT |
ZTE Corporation, Sanechips |
R2-2007778 |
Correction to 38331 on RA report |
ZTE Corporation, Sanechips |
R2-2007779 |
Inclusion of UL carrier indication in CEF report |
ZTE Corporation, Sanechips |
R2-2007954 |
Correction to RLF content setting in VarRLF-Report |
Quectel |
R2-2008000 |
Correction on the field description of CGI-InfoEUTRALogging |
Samsung Electronics Co., Ltd |
R2-2008001 |
Correction to measResultNeighCells for logged measurements |
Samsung Electronics Co., Ltd |
R2-2008002 |
Correction to the upper limit of PLMN identities in VarRLF-Report |
Samsung Electronics Co., Ltd |
R2-2008003 |
Corrections to measResultLastServCell for RLF and HO failure |
Samsung Electronics Co., Ltd |
R2-2008004 |
Corrections to mobility history information |
Samsung Electronics Co., Ltd |
R2-2008005 |
Miscellaneous corrections related to connection establishment/resume failure information |
Samsung Electronics Co., Ltd |
R2-2008006 |
Miscellaneous corrections related to logged measurements |
Samsung Electronics Co., Ltd |
R2-2008281 |
Summary of [888] RRC Corrections |
Huawei |
R2-2008284 |
Editorial corrections on MDT and SON in NR |
Huawei, HiSilicon |
R2-2008285 |
Correction to MDT features |
Huawei, HiSilicon |
R2-2008286 |
Correction to SON features |
Ericsson |
R2-2008287 |
Correction to SON features |
Ericsson |
R2-2008401 |
Summary of [888] RRC corrections |
Huawei |
6.11.1 |
General and Stage-2 Corrections |
|
R2-2006817 |
Missing RACH Figure |
Nokia (Rapporteur), Nokia Shanghai Bell, OPPO, ZTE |
6.11.2 |
User plane corrections |
|
R2-2006548 |
Remaining Issues on Fallback Reception in the 2-step CFRA |
vivo |
R2-2007825 |
Correction to description of MAC subheader for msgB |
Huawei, HiSilicon |
6.11.3 |
Control plane corrections |
|
R2-2006577 |
Clarification on 2-step RACH capability |
vivo |
R2-2006708 |
Correction to msgB-ResponseWindow |
vivo |
R2-2006709 |
Correction to msgA-TransMax |
vivo |
R2-2007022 |
The remaining issue on RO configuration of 2-step CFRA |
Fujitsu |
R2-2007826 |
Correction on RACH-ConfigCommonTwoStepRA |
Huawei, HiSilicon |
R2-2007827 |
Correction on msgA-PUSCH-Config |
Huawei, HiSilicon |
R2-2008012 |
Further discussion on 2-step RA configurations |
LG Electronics |
R2-2008543 |
Correction on msgA-PUSCH-Config |
Huawei, HiSilicon |
6.12 |
NR Other Control Plane WIs |
|
R2-2006516 |
LS reply on RACS multiple radio capability formats (R3-204147; contact: Huawei) |
RAN3 |
R2-2006633 |
Correction on First NPN-Identity Usage for SIB Validity |
CATT |
R2-2006634 |
Correction on Naming of the List of Forbidden Tracking Areas |
CATT |
R2-2006852 |
Cell selection and reselection corrections for NPNs |
Nokia, Nokia Shanghai Bell |
R2-2006853 |
Corrections for PNI-NPN related parameter selection |
Nokia, Nokia Shanghai Bell |
R2-2006879 |
Correction to the support of NR-DC for PNI-NPN |
Lenovo, Motorola Mobility |
R2-2006884 |
Clarification on CG-ConfigInfo for NR-DC and NE-DC |
Google Inc. |
R2-2006885 |
Clarification on CG-ConfigInfo for NR-DC and NE-DC |
Google Inc. |
R2-2007404 |
Limited services and SNPN Access Mode |
Ericsson |
R2-2007411 |
ims-EmergencySupport interpretation and clarification for SNPN |
Ericsson |
R2-2007805 |
Correction on the UE Capability presence upon SN addition and SN change |
Huawei, HiSilicon |
R2-2007806 |
CR on UE capability of segmentation for UE capability information |
Huawei, HiSilicon |
R2-2007807 |
CR on UE capability of segmentation for UE capability information |
Huawei, HiSilicon |
R2-2007841 |
Correction to 38.304 on any cell seletion in NPN |
Huawei, HiSilicon |
R2-2007842 |
Correction to 38.331 on SIB validity and emergency services for NPN |
Huawei, HiSilicon |
R2-2007902 |
38.304 Correction on UE behavior when the best cell is not suitable |
vivo |
R2-2008016 |
Corrections to IntraFreqCAG-CellPerPLMN and InterFreqCAG-CellList in SIB3 and SIB4 |
Samsung Electronics Co., Ltd |
R2-2008104 |
Correction on the UE Capability presence upon SN addition and SN change |
Huawei, HiSilicon, Ericsson |
R2-2008114 |
38.304 Correction on UE behavior when the best cell is not suitable |
vivo |
R2-2008183 |
Summary of offline 103 - RACS corrections |
Huawei, HiSilicon |
R2-2008184 |
Summary of [AT111][104][PRN] Stage 3 Corrections |
Nokia |
R2-2008204 |
Correction on the UE Capability presence upon SN addition and SN change |
Huawei, HiSilicon, Ericsson |
R2-2008205 |
CR on UE capability of segmentation for UE capability information |
Huawei, HiSilicon |
R2-2008206 |
CR on UE capability of segmentation for UE capability information |
Huawei, HiSilicon |
R2-2008207 |
Idle mode corrections for NPN |
Nokia, Nokia Shanghai Bell, CATT, Vivo, Huawei, HiSilicon |
R2-2008208 |
Clarification on CG-ConfigInfo for NR-DC and NE-DC |
Google Inc., Ericsson, Huawei |
R2-2008209 |
Summary of offline 104 - PRN corrections - second round |
Nokia |
R2-2008210 |
Clarification on CG-ConfigInfo for NR-DC and NE-DC |
Google Inc., Ericsson, Huawei |
R2-2008215 |
Corrections for NPNs |
Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, HiSilicon |
6.13.1 |
User plane corrections |
|
R2-2006779 |
Corrections to description of Candidate RS ID in BFR MAC CE |
Samsung Electronics Co., Ltd |
R2-2006797 |
Clarification on the BFR MAC CE report |
vivo |
R2-2007485 |
Correction on the BFR cancellation |
Nokia, Nokia Shanghai Bell |
R2-2007525 |
CR on 38.321 for BFR MAC CE design |
ZTE Corporation, Sanechips |
R2-2007526 |
CR on 38.321 for BFR procedue |
ZTE Corporation, Sanechips |
R2-2007544 |
Correction on the definition of Ci field in BFR MAC CE |
Qualcomm Incorporated |
R2-2007575 |
On serving cell set based SRS spatial relation indication MAC CE |
Ericsson |
R2-2007736 |
BFR Cancellation regarding MAC reset |
ASUSTek |
R2-2007895 |
Correction on AP and SP SRS MAC-CE |
Asia Pacific Telecom co. Ltd |
R2-2008053 |
Correction on the definition of Ci field in BFR MAC CE |
Qualcomm Incorporated |
R2-2008181 |
[Draft] Summary of offline 101 - MAC corrections for eMIMO |
Samsung |
R2-2008194 |
Corrections to description of Candidate RS ID in BFR MAC CE |
Samsung Electronics Co., Ltd |
R2-2008195 |
Correction on the BFR cancellation |
Nokia, Nokia Shanghai Bell |
R2-2008196 |
Correction on AP and SP SRS MAC-CE |
Asia Pacific Telecom co. Ltd, Ericsson |
R2-2008197 |
Summary of offline 101 - MAC corrections for eMIMO - second round |
Samsung |
R2-2008219 |
Correction on BFR MAC CE generation |
Qualcomm Incorporated, Samsung |
R2-2008221 |
Summary of offline 101 - MAC corrections for eMIMO - second round |
Samsung |
R2-2008562 |
Corrections to SUL field in SRS Spatial Relation Indication MAC CE |
Samsung |
R2-2008615 |
LS on detail MIMO MAC CE operations (R2-2005811) (R1-2007197; contact: Samsung) |
RAN1 |
6.13.2 |
Control plane corrections |
|
R2-2007161 |
Correction on number of CORESETs per BWP |
OPPO |
R2-2007577 |
Miscellaneous eMIMO corrections |
Ericsson |
R2-2008198 |
Correction on number of CORESETs per BWP |
OPPO |
R2-2008199 |
Miscellaneous eMIMO corrections |
Ericsson |
R2-2008217 |
[AT111e][112][EMIMO] RRC CR (Ericsson) |
Ericsson (Email discussion rapporteur) |
R2-2008222 |
Correction on number of CORESETs per BWP |
OPPO, Ericsson |
R2-2008223 |
Correction on number of CORESETs per BWP |
OPPO |
R2-2008224 |
Correction on number of CORESETs per BWP |
Ericsson, OPPO |
R2-2008225 |
Correction on number of CORESETs per BWP |
Ericsson, OPPO |
R2-2008226 |
Miscellaneous eMIMO corrections |
Ericsson |
R2-2008563 |
Summary of [POST111e][112][eMIMO] RRC Corrections |
Ericsson |
R2-2008564 |
Miscellaneous eMIMO corrections |
Ericsson, Nokia, Nokia Shanghai Bell |
R2-2008609 |
LS on multi-CC simultaneous TCI activation with multi-TRP/panel transmission (R1-2007203; contact: LGE) |
RAN1 |
6.14 |
NR Other R1 WIs |
|
R2-2008608 |
Reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI (R1-2007187; contact: ZTE) |
RAN1 |
6.14.2 |
Control plane corrections |
|
R2-2006524 |
Response LS on Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI R3-204399; contact: ZTE) |
RAN3 |
R2-2006898 |
Discussion on RAN3 LS about SRS exchange |
ZTE Corporation, Sanechips |
R2-2006899 |
Draft reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI |
ZTE Corporation |
R2-2007080 |
PUCCH configuration with subslotLengthForPUCCH-r16 |
CATT |
R2-2007355 |
Exchange of SRS Information across GNB for UE CLI |
Nokia, Nokia Shanghai Bell |
R2-2007356 |
[Draft ]Reply LS to the LS on Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI |
Nokia, Nokia Shanghai Bell |
R2-2007851 |
Draft LS on Update frequency of SRS-RSRP configuration for CLI |
Samsung |
R2-2007862 |
Converting suffix ForDCI-Formatx-y for shorter RRC parameter names |
Huawei, HiSilicon |
R2-2007989 |
CR on CLI configuration |
LG Electronics Inc. |
R2-2008182 |
Draft reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI |
ZTE Corporation |
R2-2008200 |
Draft reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI |
ZTE Corporation |
R2-2008201 |
CR on CLI configuration |
LG Electronics Inc. |
R2-2008202 |
PUCCH configuration with subslotLengthForPUCCH-r16 |
CATT |
R2-2008203 |
Miscellaneous RRC corrections for NR eURLLC |
Huawei, HiSilicon, CATT |
R2-2008218 |
CLI configuration |
LG Electronics |
R2-2008220 |
Reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI |
RAN2 |
R2-2008405 |
Draft reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI |
ZTE |
6.15 |
NR Other R4 WIs |
|
R2-2006808 |
Discussion on UE FR2 P-MPR reporting |
OPPO |
R2-2006809 |
Draft Response LS on UE FR2 P-MPR reporting |
OPPO |
R2-2006895 |
CR to 38.306 on introducing power boosting in UL Tx switching CA case |
ZTE Corporation, Sanechips, China Telecom, Huawei, HiSilicon, OPPO |
R2-2006896 |
CR to 38.331 on introducing power boosting in UL Tx switching CA case |
ZTE Corporation, Sanechips, China Telecom, Huawei, HiSilicon, OPPO |
R2-2006985 |
Discussion on remained issues of UL Tx switching |
China Telecom |
R2-2007001 |
Correction on CSI-RS Based Intra-frequency and Inter-frequency Measurement Definition |
CATT, ZTE Corporation, Sanechips, Huawei, HiSilicon |
R2-2007002 |
Correction on CSI-RS based intra-frequency and inter-frequency measurement definitionCorrection on CSI-RS Based Intra-frequency and Inter-frequency Measurement Definition |
CATT, ZTE Corporation, Sanechips, Huawei, HiSilicon |
R2-2007065 |
NR CA additional spectrum emission requirements |
Nokia, Nokia Shanghai Bell |
R2-2007082 |
Introduction on frequency separation class for DL-only FR2 spectrum |
Apple, Ericsson |
R2-2007083 |
Introduction on frequency separation class for DL-only FR2 spectrum |
Apple, Ericsson |
R2-2007085 |
Remaining issues on UL switching |
Apple, OPPO |
R2-2007086 |
Draft LS on UE capability derivation from 2Tx to 1Tx in UL Tx switching |
Apple |
R2-2007087 |
Fallback band combination exception for UL Tx switching |
Apple, China Telecom, OPPO |
R2-2007123 |
P-MPR Reporting |
Apple |
R2-2007152 |
Discussion on the MPE enhancements |
vivo |
R2-2007153 |
Draft CR on supporting the MPE enhancements |
vivo |
R2-2007154 |
Draft CR on supporting the MPE enhancements |
vivo |
R2-2007375 |
UE FR2 MPE enhancements and solutions |
Nokia, Nokia Shanghai Bell |
R2-2007376 |
Introduction of MPE reporting for FR2 |
Nokia, Nokia Shanghai Bell |
R2-2007377 |
Introduction of MPE reporting for FR2 |
Nokia, Nokia Shanghai Bell |
R2-2007378 |
Introduction of MPE reporting for FR2 |
Nokia, Nokia Shanghai Bell |
R2-2007379 |
Introduction of MPE reporting for FR2 |
Nokia, Nokia Shanghai Bell |
R2-2007380 |
Uplink power boosting via suspended IBE requirements |
Nokia, Nokia Shanghai Bell |
R2-2007381 |
Uplink power boosting via suspended IBE requirements |
Nokia, Nokia Shanghai Bell |
R2-2007403 |
DL-only spectrum |
Ericsson, Apple |
R2-2007533 |
Enhancement on FR2 MPE Mitigation |
ZTE Corporation, Sanechips |
R2-2007604 |
Remaining issues for UL Tx Switching |
Ericsson |
R2-2007649 |
L2/3 aspects of MPE mitigation |
InterDigital |
R2-2007650 |
Summary of MPE mitigation in FR2 |
InterDigital |
R2-2007651 |
Addition of MPE reporting to TS 38.321 |
InterDigital |
R2-2007652 |
Addition of MPE reporting to TS 38.331 |
InterDigital |
R2-2007949 |
Remaining issues on dynamic UL Tx switching |
Huawei, HiSilicon, ZTE Corporation, Sanechips |
R2-2007950 |
CR on clarification of fallback BC and prerequisite of CA case in supportedBandCombinationList-UplinkTxSwitch |
Huawei, HiSilicon, ZTE Corporation, Sanechips |
R2-2008093 |
Discussion on MPE enhancements |
Ericsson |
R2-2008094 |
Implementing MPE enhancements |
Ericsson |
R2-2008095 |
Implementing MPE enhancements |
Ericsson |
R2-2008096 |
Implementing MPE enhancements |
Ericsson |
R2-2008100 |
CR on clarification of fallback BC and prerequisite of CA case in supportedBandCombinationList-UplinkTxSwitch |
Huawei, HiSilicon, China Telecom, ZTE Corporation, Sanechips |
R2-2008106 |
Discussion on fallback-BC for UL TX switching |
OPPO |
R2-2008241 |
MPE Reporting Phase 2 |
InterDigital |
R2-2008415 |
UL-TX-Switch Capabilities – Alternative to parallel list of BCs |
Ericsson |
R2-2008416 |
Summary for Offline [AT111-e][040][TEI16] SMTC and NeedforGap Corrections |
Nokia, Nokia Shanghai Bell |
R2-2008453 |
Uplink power boosting via suspended IBE requirements |
Nokia, Nokia Shanghai Bell |
R2-2008454 |
Uplink power boosting via suspended IBE requirements |
Nokia, Nokia Shanghai Bell |
R2-2008462 |
Introduction on enhanced frequency separation class and frequency separation class for DL-only FR2 spectrum |
Apple, Ericsson |
R2-2008463 |
Introduction on enhanced frequency separation class and frequency separation class for DL-only FR2 spectrum |
Apple, Ericsson |
R2-2008487 |
Summary of offline-036 CSIRS L3 and RF FR1 (CATT) |
CATT |
R2-2008510 |
Addition of MPE reporting to TS 38.321 |
InterDigital |
R2-2008511 |
Addition of MPE reporting to TS 38.331 |
InterDigital |
R2-2008512 |
Summary of offline 037 on FR2 MPE Reporting |
InterDigital |
R2-2008570 |
Introduction of MPE reporting |
InterDigital, Ericsson, Nokia, Nokia Shanghai Bell |
R2-2008571 |
LS on MPE enhancements (R4-2011733; contact: Nokia) |
RAN4 |
R2-2008575 |
Addition of MPE reporting to TS 38.306 |
InterDigital |
R2-2008577 |
LS on additional DC location reporting for intra-band UL CA (R4-2011722; contact: Qualcomm) |
RAN4 |
R2-2008578 |
LS on FR1 intra-band UL CA UE capability (R4-2011724; contact: Huawei) |
RAN4 |
R2-2008595 |
Introduction of MPE reporting |
InterDigital, Ericsson, Nokia, Nokia Shanghai Bell |
R2-2008621 |
Uplink power boosting via suspended IBE requirements |
Nokia, Nokia Shanghai Bell |
R2-2008622 |
Uplink power boosting via suspended IBE requirements |
Nokia, Nokia Shanghai Bell |
R2-2008659 |
Configuration for uplink power boosting via suspended IBE requirements |
Nokia, Nokia Shanghai Bell |
6.16 |
NR Other |
|
R2-2006502 |
Reply LS on support of eCall over NR (C1-203221; contact: Qualcomm) |
CT1 |
R2-2006533 |
Reply LS to Reply LS on support for eCall over NR (S5-203369; contact: Nokia) |
SA5 |
R2-2006538 |
LS on mandatory support of full rate user plane integrity protection for 5G (SP-200617; contact: DT) |
SA |
R2-2006539 |
LS on 3GPP NR Rel-16 URLLC and IIoT performance evaluation (WI042_2020_06_29_5G_ACIA_LS_WI042_to_3GPP-RAN1; contact: Bosch, Ericsson, ZVEI) |
5G-ACIA |
R2-2006715 |
Mandatory Integrity protection at full user data rate |
Intel Corporation, Deutsche Telekom |
R2-2006825 |
Mandatory support of full rate user plane integrity protection |
Deutsche Telekom, BT, Huawei, HiSilicon, Nokia, T-Mobile USA, Siemens, Telecom Italia, ORANGE, BMWi, Telstra, Telefonica, Swift Navigation, Vodafone, NCSC, KPN, Erillisverkot, AT&T, Intel Corporation, Ericsson, Telia Company, BOSCH, A.S.T.R.I.D. S.A., NTT DOCOMO INC, SEQUANS |
R2-2006826 |
Mandatory support of full rate user plane integrity protection in NR-DC |
Deutsche Telekom, Telecom Italia, BMWi, Siemens, NCSC, Vodafone, Broadcom, Bell Mobility, AT&T, ORANGE, BT, KPN, Erillisverkot, Telstra, Swift Navigation, BOSCH, SEQUANS, FirstNet, T-Mobile USA, Intel Corporation, Huawei, HiSilicon, Telefonica, Ericsson |
R2-2006907 |
Mandatory support of UPIP at full data rate for NR |
Qualcomm Incorporated |
R2-2006908 |
Mandatory support of User Plane Integrity Protection at full data rate |
Qualcomm Incorporated |
R2-2006909 |
Draft Reply LS on mandatory support of full rate UPIP for 5G |
Qualcomm Incorporated |
R2-2007062 |
38321 CR Corrections on Secondary DRX |
LG Electronics Inc. |
R2-2007117 |
SMTC Configuration for PSCell Addition and SN Change in NR-DC |
Apple, MediaTek Inc., Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE Corporation, Sanechips, CATT |
R2-2007118 |
SMTC Configuration for PSCell Addition and SN Change in NR-DC |
Apple, MediaTek Inc., Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE Corporation, Sanechips, CATT |
R2-2007231 |
UE requirements on ASN.1 comprehension covering early implementation |
Samsung Telecommunications |
R2-2007234 |
Discussion on UE behaviours for access barring alleviation |
Google Inc. |
R2-2007258 |
Correction to secondaryDRX-Group capability |
Ericsson |
R2-2007370 |
CR for secondary DRX group |
OPPO |
R2-2007426 |
Discussion on SIB24 issue |
CMCC |
R2-2007486 |
Miscellaneous corrections for multiple DRX groups |
Nokia, Nokia Shanghai Bell |
R2-2007549 |
On combined RRC procedures |
Nokia, Nokia Shanghai Bell, Ericsson |
R2-2007557 |
RRC processing delays for combined procedures |
Nokia, Nokia Shanghai Bell, Ericsson |
R2-2007586 |
[draft] Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G |
Deutsche Telekom |
R2-2007638 |
[draft] LS on mandatory support of full rate user plane integrity protection for 5G |
Intel Corporation |
R2-2007849 |
Correction to gapIndication considering interFrequencyConfig-NoGap |
Samsung |
R2-2007890 |
(Re)start condition of drx-shortCycleTimer for secondary DRX |
MediaTek Inc. |
R2-2007945 |
FR2 inter-RAT measurement gap requirement indication |
Nokia, Nokia Shanghai Bell |
R2-2007948 |
Correction on HO from NR to EN-DC |
Huawei, HiSilicon |
R2-2007959 |
CR to 36.300 on support of NeedForGap capability |
Nokia, Nokia Shanghai Bell |
R2-2007960 |
Introduction of CR containing early implementable feature |
Huawei, HiSilicon |
R2-2007962 |
Correction to RRC connection release procedure without security for EN-DC cell reselection |
Samsung Electronics Co., Ltd |
R2-2008007 |
CR on UE behavior with E-UTRA cell selection upon mobility from NR failure for enhanced EPS voice fallback |
Samsung Electronics Co., Ltd |
R2-2008067 |
Issue on ping pong state transition for sidelink UE |
Xiaomi communications, China Mobile, Apple, Huawei |
R2-2008068 |
Introduction of Sidelink Data Inactivity monitoring |
Xiaomi communications, China Mobile, Apple, Huawei |
R2-2008069 |
Introduction of Sidelink Data Inactivity monitoring |
Xiaomi communications, China Mobile, Apple, Huawei |
R2-2008070 |
Introduction of Sidelink Data Inactivity monitoring |
Xiaomi communications, China Mobile, Apple, Huawei |
R2-2008367 |
Discussion on SIB24 issue |
CMCC |
R2-2008392 |
Issue on ping pong state transition for sidelink UE |
Xiaomi communications, China Mobile, Apple, Huawei, vivo |
R2-2008458 |
Reply LS on mandatory support of full rate user plane integrity protection for 5G (R3-205653; contact: Qualcomm) |
RAN3 |
R2-2008464 |
CR to 36.300 on support of NeedForGap capability |
Nokia, Nokia Shanghai Bell |
R2-2008477 |
SMTC Configuration for PSCell Addition and SN Change in NR-DC |
Apple, MediaTek Inc., Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE Corporation, Sanechips, CATT |
R2-2008491 |
LS Reply on QoS Monitoring for URLLC (S5-204537; contact: Intel) |
SA5 |
R2-2008509 |
Correction on HO from NR to EN-DC |
Huawei, HiSilicon |
R2-2008513 |
Mandatory support of full rate user plane integrity protection |
Deutsche Telekom, BT, Huawei, HiSilicon, Nokia, T-Mobile USA, Siemens, Telecom Italia, ORANGE, BMWi, Telstra, Telefonica, Swift Navigation, Vodafone, NCSC, KPN, Erillisverkot, AT&T, Intel Corporation, Ericsson, Telia Company, BOSCH, A.S.T.R.I.D. S.A., NTT DOCOMO INC, QUALCOMM, SEQUANS, Broadcom, FirstNet, Bell Mobility |
R2-2008515 |
Summary for [Offline-041][TEI16] Other Corrections |
Huawei, HiSilicon |
R2-2008524 |
Correction to RRC connection release procedure without security for EN-DC cell reselection |
Samsung |
R2-2008525 |
CR on UE behavior with E-UTRA cell selection upon mobility from NR failure for enhanced EPS voice fallback |
Samsung |
R2-2008611 |
Correction to secondaryDRX-Group capability |
Ericsson |
R2-2008612 |
Corrections to secondary DRX |
Ericsson, LG, OPPO, Nokia, Nokia Shanghai Bell |
R2-2008620 |
CR to 36.300 on support of NeedForGap capability |
Nokia, Nokia Shanghai Bell |
R2-2008639 |
Mandatory support of full rate user plane integrity protection in MR-DC |
Deutsche Telekom, Intel Corporation, Broadcom, CMCC, Futurewei, Mediatek, Qualcomm, Telstra, Vodafone, Swift Navigation, BOSCH, Erillisverkot, KPN, ORANGE, Siemens, BMWi, Ericsson, SEQUANS |
R2-2008640 |
[draft] Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G |
Deutsche Telekom |
R2-2008643 |
Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G |
RAN2 |
R2-2008684 |
CR to 36.300 on support of NeedForGap capability |
Nokia, Nokia Shanghai Bell |
7.1.1 |
Cross WI RRC corrections |
|
R2-2006839 |
Correction on initiation of RRCConnectionReestablishmentRequest |
Ericsson, ETRI |
R2-2006850 |
Correction on schedulingRequestConfig release |
ZTE Corporation, Sanechips |
R2-2007737 |
Correction on RRC re-establishment procedure |
ASUSTeK |
R2-2008166 |
Correction on RRC Connection re-establishment |
Huawei, HiSilicon, Ericsson, ETRI, ASUSTeK |
R2-2008167 |
Correction on NB-IoT process under conditionalReconfiguration |
ZTE Corporation, Sanechips |
7.1.2 |
Feature Lists and UE capabilities |
|
R2-2006512 |
LS on further updated Rel-16 RAN1 UE features list for LTE (R1-2005118; contact: NTT DOCOMO, AT&T) |
RAN1 |
R2-2006525 |
LS on Rel-16 RAN4 UE features lists for LTE and NR (R4-2009173; contact: NTT DOCOMO) |
RAN4 |
R2-2008442 |
LS on updated Rel-16 RAN1 UE features list for LTE (R1-2007139; contact: NTT DOCOMO, AT&T) |
RAN1 |
R2-2008443 |
LS on Rel-16 RAN4 UE features lists for LTE and NR (R4-2011679; contact: CMCC) |
RAN4 |
7.1.3 |
Other |
|
R2-2007655 |
Editorial changes |
Ericsson |
R2-2008165 |
Editorial changes |
Ericsson |
7.2.4 |
Coexistence with NR corrections |
|
R2-2006858 |
Clarification on subframe level resource reservation for eMTC |
ZTE Corporation, Sanechips |
R2-2008233 |
Report of [AT111-e][403][eMTC R16] Clarification on subframe level resource reservation (ZTE) |
ZTE (email discussion rapporteur) |
R2-2008240 |
Clarification on resource reservation for eMTC |
ZTE Corporation, Sanechips |
7.2.5 |
Connection to 5GC corrections |
|
R2-2006859 |
Measurement requirement for eMTC UE in RRC_INACTIVE state |
ZTE Corporation, Sanechips |
R2-2006860 |
Draft LS to RAN4 on measurement requirement for eMTC UE in RRC_INACTIVE state |
ZTE Corporation, Sanechips |
R2-2007341 |
Corrections to connection to 5GC for eMTC |
Huawei, HiSilicon |
R2-2008234 |
LS to RAN4 on measurement requirement for eMTC UE in RRC_INACTIVE |
RAN2 |
R2-2008235 |
Corrections to connection to 5GC for eMTC |
Qualcomm Incorporated, Huawei, HiSilicon |
R2-2008237 |
Corrections to connection to 5GC for eMTC |
Qualcomm Incorporated, Huawei, HiSilicon |
7.2.6 |
Other MTC specific corrections |
|
R2-2006792 |
Early UE capability retrieval enhancements for eMTC connecetd to 5GC |
Qualcomm Inc, Sierra Wireless, Thales, Telus, ZTE Corporation, TurkCell |
R2-2007695 |
RRC CR for early UE capability retrieval for eMTC connected to 5GC |
Qualcomm Inc,Sierra Wireless, Thales, Telus, ZTE Corporation,TurkCell |
R2-2007894 |
[Draft] Reply LS on early UE capability retrieval for eMTC |
Qualcomm Inc |
R2-2008231 |
[Draft] Reply LS on early UE capability retrieval for eMTC |
Qualcomm Inc |
R2-2008238 |
Reply LS on early UE capability retrieval for eMTC |
RAN2 |
7.2.7 |
MTC UE capabilities corrections |
|
R2-2007340 |
Addition of missing capabilities for eMTC R16 |
Huawei, HiSilicon |
R2-2008236 |
Addition of missing capabilities for eMTC R16 |
Huawei, HiSilicon |
7.3.1 |
General and Stage-2 Corrections |
|
R2-2006506 |
LS on RAN1 clarification on MWUS frequency allocation (R1-2004952; contact: Ericsson) |
RAN1 |
R2-2006519 |
Reply LS on assistance indication for WUS (R3-204175; contact: Qualcomm) |
RAN3 |
R2-2007337 |
Miscellaneous corrections for Rel-16 NB-IoT |
Huawei, HiSilicon |
R2-2007338 |
Miscellaneous corrections to NB-IoT and eMTC Rel-16 enhancements |
Huawei, HiSilicon |
R2-2008303 |
Miscellaneous corrections for Rel-16 NB-IoT |
Huawei, HiSilicon |
R2-2008304 |
Miscellaneous corrections to NB-IoT and eMTC Rel-16 enhancements |
Huawei, HiSilicon, Qualcomm Incorporated |
R2-2008312 |
Corrections for Rel-16 NB-IoT and eMTC |
Huawei, HiSilicon |
R2-2008457 |
Reply LS on system support for WUS (R3-205652; contact: Qualcomm) |
RAN3 |
7.3.2 |
UE-group wake-up signal (WUS) Corrections |
|
R2-2007336 |
Corrections to GWUS |
Huawei, HiSilicon |
R2-2007567 |
Group WUS corrections |
Qualcomm Incorporated |
R2-2007568 |
WUS corrections |
Qualcomm Incorporated |
R2-2008305 |
(G)WUS corrections |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips, Huawei, HiSilicon, Ericsson |
7.3.3 |
Transmission in preconfigured resources corrections |
|
R2-2006842 |
Starting legacy TA timer for PUR fallback |
ZTE Corporation, Sanechips |
R2-2006846 |
HARQ feedback for PUR response |
ZTE Corporation, Sanechips |
R2-2006848 |
Correction on discarding PUR-RNTI |
ZTE Corporation, Sanechips |
R2-2006849 |
Other corrections on 36321 for PUR |
ZTE Corporation, Sanechips |
R2-2006980 |
Addition of PUR RNTI in E-UTRA related UE identities |
Qualcomm Inc |
R2-2007339 |
Discussion on carrier configuration for PUR |
Huawei, HiSilicon |
R2-2007365 |
Correction to discard of PUR-RNTI |
Ericsson |
R2-2007398 |
TA validation check for HARQ feeback to PUR response |
LG Electronics UK |
R2-2007738 |
Impact on D-PUR TA timer due to reconfiguration of PUR periodicity and offset |
ASUSTeK |
R2-2007739 |
HARQ feedback in RRC_IDLE |
ASUSTeK |
R2-2007901 |
CR for starting legacy TA timer for PUR fallback |
ZTE Corporation, Sanechips |
R2-2007987 |
CR for HARQ feedback for PUR response |
ZTE Corporation, Sanechips |
R2-2008307 |
Report of [AT111-e][307][NBIOT/eMTC R16] 36.321 PUR corrections (ZTE) |
ZTE (email discussion rapporteur) |
R2-2008308 |
CR for HARQ feedback for PUR response |
ZTE Corporation, Sanechips |
R2-2008314 |
MAC corrections for PUR |
ZTE Corporation, Sanechips, ASUSTeK, Ericsson, LG Electronics UK, Qualcomm Incorporated |
R2-2008315 |
TA timer corrections for PUR |
ZTE Corporation, Sanechips, Qualcomm Incorporated, ASUSTeK |
7.3.4 |
Other NB-IoT Specific corrections |
|
R2-2006851 |
Minor corrections on 36304 for NB-IoT |
ZTE Corporation, Sanechips |
R2-2007335 |
Correction to NB-IoT supported functionality in idle mode |
Huawei, HiSilicon |
R2-2008306 |
Miscellaneous corrections to NB-IoT Rel-16 enhancements |
Huawei, HiSilicon |
R2-2008313 |
Miscellaneous corrections to NB-IoT Rel-16 enhancements |
Huawei, HiSilicon, ZTE Corporation, Sanechips, Qualcomm Incorporated |
7.4.2 |
DAPS handover Corrections |
|
R2-2006682 |
Corretion on the RLF for LTE DAPS |
vivo |
R2-2006791 |
PHR reporting format for DAPS Handover |
Qualcomm Inc, Huawei, HiSilicon |
R2-2006798 |
Clarification on single entry PHR for DAPS |
vivo |
R2-2006935 |
Support of DAPS handover without key change |
Intel Corporation |
R2-2007194 |
Handling of expiry of dataInactivityTimer for DAPS |
NEC |
R2-2007268 |
Correction to RLC entities creation for DAPS |
Ericsson |
R2-2007269 |
Correction to RLC entities creation for DAPS |
Ericsson |
R2-2007270 |
Time misalignment in DAPS DRB configuration (Alt.1) |
Ericsson |
R2-2007271 |
Time misalignment in DAPS DRB configuration (Alt.2) |
Ericsson |
R2-2007272 |
Time misalignment in DAPS DRB configuration (Alt.1) |
Ericsson |
R2-2007273 |
Time misalignment in DAPS DRB configuration (Alt.2) |
Ericsson |
R2-2007274 |
Clarification of the T304 informative table for DAPS HO |
Ericsson |
R2-2007308 |
Discussion on source release indication |
Huawei, HiSilicon |
R2-2007309 |
Discussion on releasing SCells |
Huawei, HiSilicon |
R2-2007310 |
Correction on TS38.331 for RLF handling in DAPS |
Huawei, HiSilicon |
R2-2007311 |
Correction on TS38.331 for RRC connection re-establishment in DAPS |
Huawei, HiSilicon |
R2-2007358 |
Clarification on no DAPS HO in MR-DC |
Nokia, Nokia Shanghai Bell |
R2-2007456 |
Clarification on TS38.331 for DAPS |
Huawei, HiSilicon |
R2-2007481 |
Incorrect restriction for RLC UM radio bearers |
Ericsson |
R2-2007496 |
DAPS handover corrections |
Ericsson |
R2-2007497 |
DAPS handover corrections |
Ericsson |
R2-2007503 |
Corretion on the RLF for NR DAPS |
vivo |
R2-2007523 |
PHR for DAPS |
Ericsson |
R2-2007625 |
Corrections regarding the use of DAPS terminolgy |
Samsung Telecommunications |
R2-2007665 |
Corrections to T304 expiry during DAPS |
Samsung |
R2-2007666 |
Aligning terminologies for handling of L2 entities in DAPS |
Samsung |
R2-2007692 |
MAC CR for PHR reporting format for LTE DAPS handover |
Qualcomm Inc, Huawei, HiSilicon |
R2-2007693 |
RRC CR for PHR reporting for LTE DAPS handover |
Qualcomm Inc, Huawei, HiSilicon |
R2-2007710 |
No support of DAPS HO for a CHO candidate cell |
ZTE Corporation, Sanechips, Ericsson |
R2-2007711 |
No support of DAPS HO for a CHO candidate cell |
ZTE Corporation, Sanechips, Ericsson |
R2-2007788 |
Correction for SRB handling of DAPS HOF (36.331) |
SHARP Corporation |
R2-2007789 |
Correction for SRB handling of DAPS HOF (38.331) |
SHARP Corporation |
R2-2007790 |
Potential security issue on DAPS handover |
SHARP Corporation |
R2-2007791 |
[Draft] LS to SA3 on security handling for DAPS handover |
SHARP Corporation |
R2-2007893 |
Correction for PDCP status report |
LG Electronics Inc. |
R2-2007903 |
Clarification on the UEAssistanceInformation for DAPS |
vivo |
R2-2008072 |
Correction on TS36.331 for RLF handling in DAPS |
Huawei, HiSilicon |
R2-2008073 |
Correction on TS36.331 for RRC connection re-establishment in DAPS |
Huawei, HiSilicon |
R2-2008074 |
Correction on TS36.300 for uplink data switching in DAPS |
Huawei, HiSilicon |
R2-2008075 |
Correction on TS38.300 for source fallback in DAPS |
Huawei, HiSilicon |
R2-2008076 |
Correction on TS38.300 for uplink data switching in DAPS |
Huawei, HiSilicon |
R2-2008134 |
Report of [AT111-e][204][MOB] DAPS corrections (Huawei) |
Huawei, HiSilicon |
R2-2008169 |
Clarification on TS38.331 for DAPS |
Huawei, HiSilicon |
R2-2008174 |
Correction for PDCP status report |
LG Electronics Inc. |
R2-2008409 |
drb-continueROHC for DAPS |
Ericsson, Samsung |
R2-2008455 |
Corretion on the RLF for LTE DAPS |
vivo, Ericsson |
R2-2008456 |
Corretion on the RLF for NR DAPS |
vivo, Ericsson |
R2-2008679 |
Corretion on the RLF for LTE DAPS |
vivo, Ericsson |
R2-2008680 |
Corretion on the RLF for NR DAPS |
vivo, Ericsson |
7.4.3 |
UE capability corrections |
|
R2-2006932 |
Correction on LTE MOB capability |
Intel Corporation, China Telecom, Samsung |
R2-2006933 |
Correction on LTE MOB capability |
Intel Corporation, China Telecom, Samsung |
R2-2007458 |
Correction on TS 36.331 for DAPS UE capabilities |
Huawei, HiSilicon |
R2-2007459 |
Correction on TS 36.306 for DAPS |
Huawei, HiSilicon |
R2-2008136 |
Summary of discussion [AT111-e][206][MOB] UE capability corrections for mobility (China Telecom) |
China Telecom |
R2-2008175 |
Correction on TS 36.331 for DAPS UE capabilities |
Huawei, HiSilicon |
R2-2008176 |
Correction on TS 36.306 for DAPS |
Huawei, HiSilicon |
R2-2008557 |
Correction on LTE MOB capability |
Intel Corporation, China Telecom, Samsung |
R2-2008565 |
Correction on LTE MOB capability |
Intel Corporation, China Telecom, Samsung |
R2-2008566 |
Correction on LTE MOB capability |
Intel Corporation, China Telecom, Samsung |
R2-2008625 |
Making multipleTimingAdvance conditionally mandatory for DAPS |
Ericsson |
R2-2008626 |
Restructuring DAPS capabilities |
Ericsson |
7.4.4 |
Other corrections |
|
R2-2007762 |
Correction on CHO for LTE-5GC |
Huawei, HiSilicon |
R2-2007763 |
Correction on TS 36.300 for CHO |
Huawei, HiSilicon |
R2-2008520 |
Correction on TS 36.300 for CHO |
Huawei, HiSilicon |
7.5 |
LTE Other WIs |
|
R2-2007518 |
Clarification to Fallback band combination definition |
Nokia, Nokia Shanghai Bell |
R2-2007697 |
Correction on T312 timer information |
ZTE Corporation, Sanechips |
R2-2007844 |
Minor changes collected by Rapporteur |
Samsung |
R2-2008160 |
Minor changes collected by Rapporteur |
Samsung |
R2-2008607 |
LS on Updates to TS 36.300 on terrestrial broadcast (R1-2007154; contact: Qualcomm) |
RAN1 |
8.1.1 |
Organizational, Requirements, Scope and Architecture |
|
R2-2006574 |
Overview on NR MBS Architecture |
MediaTek Inc. |
R2-2006593 |
Discussion on Requirement and Architecture of MBS |
CATT |
R2-2006793 |
NR Multicast Radio Bearer Architecture aspects |
Qualcomm Inc |
R2-2006804 |
General considerations for MBS in RRC_CONNECTED |
OPPO |
R2-2006952 |
Consideration of L2 protocol impact by MBS |
Intel Corporation |
R2-2006983 |
Scope and solution approach for NR MBS |
Nokia, Nokia Shanghai Bell |
R2-2007024 |
Rel-17 NR MBS workplan |
Huawei, CMCC, HiSilicon |
R2-2007025 |
Stage 2 aspects for NR MBS |
Huawei, HiSilicon |
R2-2007033 |
Overview of NR MBS |
vivo |
R2-2007124 |
RAN2 Study on the NR MBMS |
Apple |
R2-2007177 |
NR multicast architecture and SC-PTM |
Sony |
R2-2007412 |
Initial considerations of NR Multicast |
CMCC |
R2-2007442 |
Scope and Architecture analysis of NR MBS |
ZTE, Sanechips |
R2-2007550 |
Discuss NR MBS architecture and protocol stack |
Futurewei |
R2-2007636 |
General framework for MBS |
Intel Corporation |
R2-2007639 |
Overview of NR MBS work item |
Ericsson |
R2-2007672 |
On Stage-2 aspects and overview of NR MBS |
Samsung |
R2-2007774 |
Initial consideration of NR MBS |
Kyocera |
R2-2007993 |
Consideration on BWP and beam in NR multicast |
LG Electronics Inc. |
R2-2008031 |
Discussion on user-plane structure for NR multicast |
LG Electronics Inc. |
8.1.2.1 |
Dynamic PTM PTP switch with service continuity |
|
R2-2006569 |
Radio Bearer based Multicast PTM and PTP mode switching |
TCL Communication Ltd. |
R2-2006575 |
UE Reception Model of NR MBS Radio Bearer and its Dynamic PTM/PTP switch |
MediaTek Inc. |
R2-2006594 |
Discussion on Dynamic PTM and PTP Switch with Service Continuity |
CATT |
R2-2006794 |
NR Multicast dynamic PTM PTP switch with service continuity |
Qualcomm Inc |
R2-2006803 |
Dynamic PTM and PTP switching with service continuity |
OPPO |
R2-2006982 |
Dynamic change between PTM and PTP transmission in gNB |
Nokia, Nokia Shanghai Bell |
R2-2007015 |
Simultaneous transmission of multicast/unicast |
NEC |
R2-2007026 |
Dynamic switch between PTP and PTM for MBS bearer |
Huawei, HiSilicon |
R2-2007034 |
Dynamic PTM PTP switch for RRC Connected UE |
vivo |
R2-2007053 |
Consideration on switching between PTP and PTM |
Spreadtrum Communications |
R2-2007134 |
Discussion on delivery mode switch with service continuity in NR multicast |
KT Corp. |
R2-2007178 |
NR multicast in connected mode |
Sony |
R2-2007248 |
Counting scheme for dynamically switching PTM and PTP |
ITRI |
R2-2007413 |
Discussion on dynamic delivery mode switch |
CMCC |
R2-2007443 |
Delivery mode switching for NR MBS |
ZTE, Sanechips |
R2-2007466 |
Protocols and Dynamic Switching for 5G MBS PTP and PTM |
Lenovo, Motorola Mobility |
R2-2007551 |
Discuss dynamic change of MBS delivery method |
Futurewei |
R2-2007631 |
Protocol structure and bearer modelling for NR MBS |
Ericsson |
R2-2007637 |
Dynamic switch between PTM and PTP for service continuity |
Intel Corporation |
R2-2007992 |
Dynamic bearer type change |
LG Electronics Inc. |
R2-2008063 |
Transfer Type Change with Service Continuity |
Samsung |
8.1.2.2 |
Mobility with Service continuity |
|
R2-2006595 |
Discussion on Mobility with Service Continuity in RRC_CONNECTED |
CATT |
R2-2006796 |
NR Multicast mobility enhancements with service continuity |
Qualcomm Inc |
R2-2006802 |
Discussion on mobility with MBS Service continuity |
OPPO |
R2-2006827 |
Scenarios and Requirements for Mobility with Service Continuity |
MediaTek Inc. |
R2-2006984 |
Service Continuity for Connected mode UE |
NEC |
R2-2007027 |
Service continuity during mobility for MBS |
Huawei, HiSilicon |
R2-2007035 |
MBS Service Continuity for RRC Connected UE |
vivo |
R2-2007054 |
Discussion on Mobility with Service continuity for connected UE |
Spreadtrum Communications |
R2-2007414 |
Discussion on MBS mobility with service continuity |
CMCC |
R2-2007444 |
Discussion about basic mobility support in NR MBS |
ZTE, Sanechips |
R2-2007467 |
PDCP Count Value Alignment to support of Loss-less handover for 5G MBS |
Lenovo, Motorola Mobility |
R2-2007552 |
Support MBS service continuity with mobility |
Futurewei |
R2-2007628 |
Mobility for NR MBS |
Ericsson |
R2-2007991 |
MBS service continuity |
LG Electronics Inc. |
R2-2008061 |
MBS Mobility for Connected Mode UEs |
Samsung |
8.1.2.3 |
Other |
|
R2-2006576 |
Reliability Improvement for NR MBS Reception |
MediaTek Inc. |
R2-2006596 |
Discussion on the Reliability of Broadcast/Multicast Service |
CATT |
R2-2007028 |
Reliability enhancement and dynamic control of transmission area for NR MBS |
Huawei, HiSilicon |
R2-2007036 |
Discussion on dynamic control of transmission area for MBS |
vivo |
R2-2007415 |
Discussion on MBS dynamic area control and reliability enhancements |
CMCC |
R2-2007445 |
Miscellaneous issues in NR MBS |
ZTE, Sanechips |
R2-2007633 |
Mechanisms to improve reliability for UEs in RRC_CONNECTED |
Ericsson |
R2-2008032 |
Discussion on reliability improvement and UL feedback in NR multicast |
LG Electronics Inc. |
R2-2008062 |
Reliability Enhancement for MBS |
Samsung |
8.1.3 |
Idle and Inactive mode UEs |
|
R2-2006597 |
Consideration on Idle and Inactive mode UEs |
CATT |
R2-2006795 |
NR Multicast services and configuration for UEs in different RRC states |
Qualcomm Inc |
R2-2006801 |
Discussion on MBS reception of idle or inactive mode UE |
OPPO |
R2-2007014 |
Some consideration for IDLE mode and IN_ACTIVE mode UE |
NEC |
R2-2007029 |
IDLE/INACTIVE UE support for NR MBS |
Huawei, HiSilicon |
R2-2007037 |
Discussion on Idle and Inactive mode UEs |
vivo |
R2-2007055 |
MBS for Idle and Inactive mode UE |
Spreadtrum Communications |
R2-2007262 |
NR Multicast in Idle and Inactive mode |
Ericsson |
R2-2007416 |
Discussion on MBS supported UEs in RRC_IDLE and RRC_INACTIVE states |
CMCC |
R2-2007446 |
MBS for UE in RRC_INACTIVE/RRC_IDLE State |
ZTE, Sanechips |
R2-2007673 |
RRC IDLE/ INACTIVE aspects of NR MBS |
Samsung |
R2-2007896 |
Group Based MBS Notification for Idle/Inactive mode UEs |
MediaTek Inc. |
R2-2008052 |
NR MBS solution for UE in RRC_IDLE or RRC_INACTIVE state |
CHENGDU TD TECH LTD. |
8.2.1 |
Organizational, Requirements and Scope |
|
R2-2007676 |
Work plan for R17 Further MR-DC enhancements WI |
Huawei |
R2-2007677 |
Status of the work on efficient SCell activation/deactivation |
Huawei |
8.2.2 |
Efficient activation / deactivation mechanism for one SCG and SCells |
|
R2-2006756 |
On Support of Activation/Deactivation for SCG |
InterDigital |
R2-2006806 |
Discussion on SCG suspension |
OPPO |
R2-2006900 |
Framework of SCG deactivation and activation |
ZTE Corporation, Sanechips |
R2-2007009 |
Efficient Activation/Deactivation Mechanism for SCG and Scells |
CATT |
R2-2007046 |
Discussion on efficient activation mechanism for one SCG |
Spreadtrum Communications |
R2-2007068 |
On fast deactivation and activation of one SG and SCells |
Nokia, Nokia Shanghai Bell |
R2-2007109 |
Scoping the usage of SCG suspension |
Apple |
R2-2007215 |
Efficient activation and deactivation mechanism for SCG and SCells |
vivo |
R2-2007236 |
Enhancements for Rel-17 efficient activation/de-activation |
Intel Corporation |
R2-2007439 |
Consideration on dormant SCG |
CMCC |
R2-2007598 |
Efficient SCG/SCell (de)activation |
Ericsson |
R2-2007623 |
Further enhancements regarding deactivation and resumption for R17 |
Samsung Telecommunications |
R2-2007678 |
Discussion on SCG deactivation and activation |
Huawei, HiSilicon |
R2-2007748 |
Efficient SCG activation/deactivation in MR-DC |
Qualcomm Incorporated |
R2-2007867 |
Discussion on SCG suspension |
MediaTek Inc. |
R2-2007986 |
Time-efficient SCG Activation mechanism |
LG Electronics |
R2-2007994 |
Discussion of SCG activation/deactivation |
SHARP Corporation |
8.2.3 |
Conditional PSCell change / addition |
|
R2-2006695 |
Scope and scenario for CPAC |
vivo |
R2-2006757 |
Coexistence of CHO and CPC at the UE |
InterDigital |
R2-2006805 |
Discussion on conditional PSCell change and addition |
OPPO |
R2-2006901 |
Discussion on conditional PSCell addition/change |
ZTE Corporation, Sanechips |
R2-2006976 |
Overview of conditional PSCell addition |
NEC |
R2-2006977 |
Inter-SN Conditional PSCell Change |
NEC |
R2-2007010 |
Scope and basic procedure for Conditional PSCell Addition/Change ??(CPAC)? |
CATT |
R2-2007052 |
Discussion on conditional PSCell addition or change |
Spreadtrum Communications |
R2-2007089 |
Discussion on conditional PSCell change and addition |
Apple |
R2-2007130 |
Scenarios and General Principles of CPAC |
ETRI |
R2-2007237 |
Rel-17 Conditional PSCell Addition |
Intel Corporation |
R2-2007364 |
On the scope of Rel-17 CPAC |
Nokia, Nokia Shanghai Bell |
R2-2007438 |
Discussion on CPAC scenarios |
CMCC |
R2-2007553 |
Inter node CPAC procedure and configuration discussion |
Futurewei |
R2-2007599 |
Conditional reconfigurations |
Ericsson |
R2-2007624 |
Further enhancements on conditional configuration for R17 |
Samsung Telecommunications |
R2-2007679 |
Discussion on Conditional PSCell addition/change |
Huawei, HiSilicon |
R2-2007749 |
Conditional PSCell addition/change |
Qualcomm Incorporated |
R2-2007839 |
Conditional PSCell addition and change in MR-DC |
Potevio |
R2-2007985 |
Considerations of CPAC in Rel-17 |
LG Electronics |
R2-2008079 |
Remaining issues of Conditional PSCell Addition |
NTT DOCOMO INC. |
8.3 |
Multi SIM |
|
R2-2006540 |
Guidance for SA2 on Solution #16 for Key Issue 2 |
Vodafone |
R2-2006627 |
Consideration on the Work Scope for Multi-SIM |
CATT |
R2-2006807 |
Discussion on Multi-SIM |
OPPO |
R2-2006916 |
Considerations for Multi-SIM WI Objectives |
Charter Communications |
R2-2006944 |
Handling of paging collision for Multi-SIM |
Qualcomm Incorporated |
R2-2006981 |
Consideration on Multi-SIM |
China Telecom |
R2-2007129 |
Coordination of concurrent communication for Multi-SIM |
Qualcomm Incorporated |
R2-2007163 |
Work plan for Multi SIM WI |
vivo, Charter Communications |
R2-2007164 |
Initial Considerations for Multi-SIM |
vivo |
R2-2007179 |
Discussion on Multi-SIM |
Sony, Convida Wireless |
R2-2007191 |
Support for Multi-SIM Devices |
MediaTek Inc. |
R2-2007207 |
Overview of Multi-SIM |
ZTE Corporation, Sanechips |
R2-2007208 |
Consideration on the RAN2 issues on Multi-SIM |
ZTE Corporation, Sanechips |
R2-2007352 |
Clarification and Finalisation of Scope for MUSIM Work |
Nokia, Nokia Shanghai Bell |
R2-2007353 |
Paging reception for MUSIM scenario |
Nokia, Nokia Shanghai Bell |
R2-2007357 |
Support of UE capabilities coordination for Multi-USIM UEs |
China Telecommunications |
R2-2007394 |
Way forward for the progress of Multi-SIM WI in RAN2 |
Huawei, HiSilicon |
R2-2007396 |
Discussion on Multi-SIM WI Objectives 1 and 2 |
Huawei, HiSilicon |
R2-2007418 |
Discussion on the paging collision and interruption issues for multi-sim UEs |
CMCC |
R2-2007602 |
Graceful leaving for a MultiSIM device |
Ericsson |
R2-2007603 |
Paging collision avoidance |
Ericsson |
R2-2007620 |
RAN2 impacts of Multi-SIM support |
Futurewei Technologies |
R2-2007740 |
Mechanism for UE to notify network switch |
ASUSTeK |
R2-2007952 |
General consideration for solving MUSIM problems |
Xiaomi Communications |
R2-2007956 |
Discussion of the coordinated leaving problem |
Xiaomi Communications |
R2-2007961 |
Solution analysis for R17 Multi-SIM KI#2 and KI#3 |
Intel Corporation |
R2-2008020 |
General considerations on potential RAN2 works for Multi-USIM devices |
Samsung Electronics Co., Ltd |
R2-2008021 |
Overview on SA2 progress for Multi-USIM devices |
Samsung Electronics Co., Ltd |
8.4 |
NR IAB enhancements |
|
R2-2006964 |
Workplan for Rel-17 IAB |
Qualcomm Incorporated (WI Rapporteur) |
R2-2008024 |
Correction of text on measIdleCarrierListEUTRA and measIdleCarrierListNR |
LG Electronics France |
R2-2008025 |
Enhancements of Topological Resilience |
LG Electronics |
R2-2008026 |
BH RLF enhancements |
LG Electronics |
8.4.1 |
Enhancements to improve topology-wide fairness, multi-hop latency and congestion mitigation |
|
R2-2006624 |
Consideration on Topology, Routing and Transport Enhancements |
CATT |
R2-2006946 |
Congestion handling and traffic splitting in IAB |
Intel Corporation |
R2-2006960 |
Multi-hop scheduling and local routing enhancements for IAB |
AT&T |
R2-2006965 |
Simulations on fairness support in IAB topology |
Qualcomm Incorporated |
R2-2006966 |
IAB flow and congestion control enhancements |
Qualcomm Incorporated |
R2-2007019 |
Topology optimization in IAB |
NEC |
R2-2007023 |
Discussion on the Rel-17 scope of IAB enhancement |
Fujitsu |
R2-2007165 |
Discussion on RLF handling enhancements |
vivo |
R2-2007166 |
Discussion on congestion mitigation enhancements |
vivo |
R2-2007200 |
Scoping out issues of topology-wide fairness, multi-hop latency and congestion mitigation |
Samsung Electronics GmbH |
R2-2007201 |
On topology-wide fairness |
Samsung Electronics GmbH |
R2-2007295 |
Consideration on routing enhancement |
LG Electronics Inc. |
R2-2007312 |
Miscellaneous enhancements for IAB network |
ZTE, Sanechips |
R2-2007487 |
On the CP/UP separation |
Nokia, Nokia Shanghai Bell |
R2-2007658 |
Other Enhancements to IAB for NR |
Ericsson |
R2-2007659 |
User plane Latency in Multi-hop IAB Systems |
Ericsson |
R2-2007840 |
Rel. 17 IAB enhancements for fairness, multi-hop latency reduction, and congestion mitigation |
Futurewei Technologies |
R2-2007865 |
Further enhancements for R17 IAB |
Huawei, HiSilicon |
8.4.2 |
Topology adaptation enhancements, RAN2 scope |
|
R2-2006625 |
Consideration Issues on Inter-CU migration |
CATT |
R2-2006626 |
Consideration on Enhancements to Reduce Service Interruption |
CATT |
R2-2006947 |
Enhancements to establish efficient topologies |
Intel Corporation |
R2-2006948 |
Backhaul failure recovery enhancments |
Intel Corporation |
R2-2006961 |
Enhancements to support IAB topology adaptation |
AT&T |
R2-2006967 |
Enhancements to BH RLF recovery for Rel-17 IAB |
Qualcomm Incorporated |
R2-2007167 |
Consideration of Inter-CU IAB Migration |
vivo |
R2-2007313 |
Initial considerations on inter-donor migration |
ZTE, Sanechips |
R2-2007488 |
Inter-donor topology adaptation |
Nokia, Nokia Shanghai Bell |
R2-2007501 |
Scope of topology adaptation issues for Rel-17 IAB |
Samsung Electronics Romania |
R2-2007660 |
Scenarios of topology adaptation for IAB network |
Ericsson |
R2-2007689 |
Separation of CP/UP for improved CP robustness |
AT&T |
R2-2007773 |
Initial consideration of topology adaptation enhancements for eIAB |
Kyocera |
R2-2007863 |
Consideration of inter-CU migration |
Huawei, HiSilicon |
R2-2007864 |
Discussion on RLF handling issues |
Huawei, HiSilicon |
R2-2007984 |
RAN2 impacts of Rel.17 IAB topology adaptation enhancements |
Futurewei Technologies |
8.4.3 |
Duplexing enhancements, RAN2 scope |
|
R2-2007314 |
Discussion on duplexing enhancement |
ZTE, Sanechips |
8.5.1 |
Organizational |
|
R2-2006921 |
Work Plan for NR IIoT/URLLC |
Nokia |
8.5.2 |
Enhancements for support of time synchronization |
|
R2-2006635 |
Discussion on Time Synchronization in Rel-17 |
CATT |
R2-2006697 |
Discussion on enhancements for support of time synchronization |
Huawei, HiSilicon |
R2-2006701 |
Enhancements for support of time synchronization |
Ericsson |
R2-2006719 |
IIoT Enhancements for Support of Time Synchronization |
Intel Corporation |
R2-2006831 |
Enhancements for time synchronization in TSN |
ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
R2-2006864 |
Topics for time synchronization in IIoT |
Fujitsu |
R2-2006906 |
Propagation Delay Compensation for Reference Timing Delivery |
Qualcomm Incorporated |
R2-2006922 |
Discussion on enhancements for support of propagation delay compensation for accurate time synchronization |
Nokia, Nokia Shanghai Bell |
R2-2007141 |
Consideration of TSN time synchronization enhancements |
OPPO |
R2-2007145 |
Discussion on the TSN enhancements |
vivo |
R2-2007294 |
Discussion on uplink time synchronization for TSN |
NTT DOCOMO INC. |
R2-2007475 |
Considerations on time synchronization enhancement |
Lenovo, Motorola Mobility |
R2-2007611 |
On propagation delay compensation |
MediaTek Inc. |
R2-2007627 |
Enhancements for support of time synchronization |
Sequans Communications |
R2-2007999 |
Consideration on Time Synchronization for TSN in R17 |
CMCC |
R2-2008033 |
Discussion on support of time synchronization |
LG Electronics Inc. |
R2-2008059 |
Enhancements for Timing Synchronization |
Samsung |
8.5.3 |
Uplink enhancements for URLLC in unlicensed controlled environments |
|
R2-2006636 |
Uplink Enhancements for URLLC in Unlicensed Spectrum |
CATT |
R2-2006696 |
Discussion about uplink enhancements for URLLC in unlicensed controlled environments |
Huawei, HiSilicon |
R2-2006700 |
Uplink enhancements for URLLC in unlicensed controlled environments |
Ericsson |
R2-2006923 |
Configured Grant Enhancement Harmonization for NR-U and URLLC |
Nokia, Nokia Shanghai Bell |
R2-2006939 |
Uplink enhancements for URLLC in unlicensed controlled environments |
Intel Corporation |
R2-2007139 |
Consideration on URLLC over NRU |
OPPO |
R2-2007146 |
Harmonizing CG enhancements in NR-U and URLLC/IIoT |
vivo |
R2-2007204 |
Potential aspects to be considered for the enhancements for URLLC in unlicensed controlled environments |
Lenovo, Motorola Mobility |
R2-2007417 |
Discussion on CG enhancement for URLLC in unlicensed controlled environments |
CMCC |
R2-2007532 |
Disscusion on the hormination of enhanced configured grant in NRIIOT and NRU |
ZTE Corporation, Sanechips |
R2-2007614 |
IIoT operation in unlicensed controlled environments |
InterDigital |
R2-2007884 |
Support of IIoT on unlicensed spectrum |
LG Electronics UK |
R2-2007958 |
Uplink enhancements for controlled unlicensed operation |
Qualcomm Incorporated |
R2-2007988 |
Consideration on timers for URLLC/IIoT in unlicensed controlled environments |
III |
R2-2008060 |
CG Harmonization for IIOT in Unlicensed Band |
Samsung |
8.6.1 |
Organizational |
|
R2-2007125 |
RAN2 Study on the Small Data Enhancement |
Apple |
R2-2007192 |
Scope for Small Data Transmission |
Ericsson |
R2-2007447 |
Work plan for the INACTIVE small data WI |
Work Item Rapporteur (ZTE) |
8.6.2 |
UL small data transmissions for RACH-based schemes |
|
R2-2006550 |
General Considerations on Small Data Transmission |
vivo |
R2-2006551 |
Supporting Small Data Transmission via RA procedure |
vivo |
R2-2006582 |
Common aspects between RACH and CG-based scheme |
Huawei, HiSilicon |
R2-2006583 |
Small data transmission with RA-based schemes |
Huawei, HiSilicon |
R2-2006653 |
Small data transmission in RRC_IACTIVE state |
ETRI |
R2-2006713 |
SDT mechanism on RRC/non-RRC based approaches and RACH requirements |
Intel Corporation |
R2-2006714 |
Radio bearer configuration for SDT considering UE context relocation and CU/DU split |
Intel Corporation |
R2-2006772 |
Random Access based Small Data Transmission - Signaling Flow |
Samsung Electronics Co., Ltd |
R2-2006773 |
Random Access based Small Data Transmission - Details |
Samsung Electronics Co., Ltd |
R2-2006800 |
Handling of small data transmission in RRC_INACTIVE |
PANASONIC R&D Center Germany |
R2-2006824 |
The RACH-Based Small Data Transmission |
PANASONIC R&D Center Germany |
R2-2006829 |
Requirements and Solutions for INACTIVE Small Data Transmission |
MediaTek Inc. |
R2-2006830 |
Subsequent Transmission of Small data in INACTIVE |
MediaTek Inc. |
R2-2006836 |
Procedure of Small Data Transmission |
OPPO |
R2-2006837 |
The Conditions for Small Data Transmission in Inactive State |
OPPO |
R2-2006845 |
RACH based small data transmission |
ITL |
R2-2006865 |
Topics for small data transmission in INACTIVE |
Fujitsu |
R2-2006991 |
Requirements and scopes of Small Data Transmissions |
CATT |
R2-2006992 |
General procedure analysis for Small Data Transmissions |
CATT |
R2-2007047 |
Discussion on UL small data transmissions for RACH-based schemes |
Spreadtrum Communications |
R2-2007069 |
Small data transmission in RRC_INACTIVE state |
ETRI |
R2-2007126 |
Small data transmission via RACH procedure |
Apple |
R2-2007180 |
Discussion on different aspects of UL Small data transmissions in NR |
Sony |
R2-2007195 |
Initial consideration on RACH based SDT |
NEC |
R2-2007197 |
2-step and 4-step based RACH Small Data transmission |
Ericsson |
R2-2007432 |
Scheme selection and scheme switch |
CMCC |
R2-2007433 |
Basic procedure for data transmission in RRC inactive state |
CMCC |
R2-2007448 |
Selection between RRC-based and RRC-less solutions for IDT |
ZTE Corporation, Sanechips, CSPG |
R2-2007449 |
Details of RRC-based IDT |
ZTE Corporation, Sanechips, CSPG |
R2-2007469 |
UL small data transmissions in 2-step RACH and 4-step RACH |
Lenovo, Motorola Mobility |
R2-2007479 |
The basic principle for small data transmissions |
Lenovo, Motorola Mobility |
R2-2007489 |
Small data transmission over pre-configured PUSCH resources |
Nokia, Nokia Shanghai Bell |
R2-2007540 |
RACH based NR small data transmission |
Qualcomm Incorporated |
R2-2007541 |
RACH based uplink small data transmission with or without anchor relocation |
Qualcomm Incorporated |
R2-2007564 |
Design of RACH-based Small Data Transmission schemes and common aspects |
Nokia, Nokia Shanghai Bell |
R2-2007612 |
UL small data transmission in inactive state |
InterDigital |
R2-2007613 |
RACH-based UL small data transmission |
InterDigital |
R2-2007741 |
Discussion on NR RRC for small data transmission |
ASUSTeK |
R2-2007742 |
Discussion on RA procedure for small data transmission |
ASUSTeK |
R2-2007746 |
considerations on small data transmission procedure in RRC_inactive |
Beijing Xiaomi Mobile Software |
R2-2007747 |
UL transmission procedure using Pre-configured PUSCH resources in RRC_inactive |
Beijing Xiaomi Mobile Software |
R2-2007838 |
Discussion on small data transmission |
Potevio |
R2-2007953 |
Techniques for enabling NR small data transmissions in INACTIVE state |
Sierra Wireless, S.A. |
R2-2008013 |
Issues in dependency to other groups |
LG Electronics |
R2-2008015 |
Considerations on UL small data transmission |
LG Electronics |
8.7.1 |
Organizational |
|
R2-2006531 |
LS on Security Requirements for Sidelink/PC5 Relays (S2-2004750; contact: MediaTek) |
SA2 |
R2-2006601 |
Work plan of R17 SL relay |
OPPO |
R2-2006602 |
Skeleton of TR 38.836 v0.0.0 |
OPPO |
R2-2007168 |
[Draft] LS to SA3 on the security related aspects for NR sidelink relay |
CATT |
R2-2008251 |
TR 38.836 |
OPPO |
R2-2008272 |
TR 38.836 |
OPPO |
R2-2008274 |
TR 38.836 |
OPPO |
8.7.2 |
Scope, requirements, and scenarios |
|
R2-2006554 |
Discussion on sidelink relay study item scope and focus areas prioritization |
Qualcomm Incorporated |
R2-2006570 |
Scenarios and Assumptions on Sidelink Relay |
MediaTek Inc. |
R2-2006603 |
Scenarios for sidelink relay |
OPPO |
R2-2006609 |
Clarification on the Scenarios for NR Sidelink Relay |
CATT |
R2-2006717 |
Requirements, Assumptions and Supported Scenarios for NR Sidelink Relay |
Intel Corporation |
R2-2006721 |
Considerations on the Study of NR Sidelink Relay |
Futurewei |
R2-2006735 |
Initial considerations on NR sidelink relay |
ZTE Corporation, Sanechips |
R2-2006758 |
Discussion and TP on Requirements and Scenarios for SL Relays |
InterDigital |
R2-2006856 |
NR SL-based UE-to-UE relay for unicast SL |
Nokia, Nokia Shanghai Bell |
R2-2006857 |
Casting types in NR SL-based relays |
Nokia, Nokia Shanghai Bell |
R2-2006866 |
Scope, Requirements and Scenarios in NR Sidelink Relaying |
Fujitsu |
R2-2006968 |
NR sidelink relay scenarios |
Samsung Electronics Co., Ltd |
R2-2007038 |
SL relay discussion in SI phase |
vivo |
R2-2007039 |
Scope and Scenarios of SL relay |
vivo |
R2-2007043 |
Scope and scenarios on NR sidelink relay |
Spreadtrum Communications |
R2-2007099 |
Discussion on NR Sidelink Relay Scenarios |
Apple, Convida Wireless |
R2-2007202 |
High-level requirements |
Samsung Electronics GmbH |
R2-2007290 |
Service continuity scenarios for sidelink relay |
Ericsson |
R2-2007293 |
Scope and initial steps for SL relay |
Ericsson |
R2-2007626 |
Initial considerations for SL relaying |
Kyocera |
R2-2007775 |
Discussion on UE-to-network coverage extension |
ETRI |
R2-2008017 |
Scope and scenarios for NR sidelink relay |
LG Electronics Inc. |
R2-2008046 |
General considerations on working for NR SL relay |
Huawei, HiSilicon, Apple, CMCC, China Telecom, China Unicom, MediaTek Inc., Sharp, Spreadtrum, Xiaomi, ZTE Corporation, Sanechips |
R2-2008252 |
[AT111-e][603] Scope, requirements, and scenarios (Interdigital) |
Interdigital (Rapporteur) |
R2-2008264 |
[AT111-e][603] Scope, requirements, and scenarios (Interdigital) |
Interdigital (Rapporteur) |
8.7.3 |
Relaying Mechanisms and their characteristics |
|
R2-2006555 |
UE-to-network relay architecture and procedures |
Qualcomm Incorporated |
R2-2006557 |
Discussion on NR sidelink relay selection and reselection |
Qualcomm Incorporated |
R2-2006571 |
RRC States for Relaying |
MediaTek Inc. |
R2-2006572 |
Architecture Options for Sidelink Relay |
MediaTek Inc. |
R2-2006604 |
Protocol stack and CP procedure for SL relay |
OPPO |
R2-2006610 |
User and Control Plane Procedures for L2 UE-to-NW Relay |
CATT |
R2-2006611 |
L2/L3 UE-to-NW Relay Comparison |
CATT |
R2-2006639 |
L2 vs L3 - Relay (re-)Selection, Quality of Service (QoS) |
Fraunhofer HHI, Fraunhofer IIS |
R2-2006641 |
L2 vs L3 - Relay/Remote UE Authorization, Service Continuity |
Fraunhofer HHI, Fraunhofer IIS |
R2-2006718 |
Characteristics of L2 and L3 based Sidelink relaying |
Intel Corporation |
R2-2006722 |
Protocol Stack and Connection Setup Procedure of Sidelink Relay |
Futurewei |
R2-2006723 |
Service Continuity with Sidelink Relay |
Futurewei |
R2-2006724 |
QoS Control with Sidelink Relay |
Futurewei |
R2-2006736 |
Discussion on relay initiation and relay UE (re-)selection |
ZTE Corporation, Sanechips |
R2-2006737 |
Discussion on NR SL Relay Architecture |
ZTE Corporation, Sanechips |
R2-2006759 |
Discussion and TP on UE to NW Relay Based on L2 Relay Architecture |
InterDigital |
R2-2006760 |
Discussion and TP on UE to UE Relay Based on L2 Relay Architecture |
InterDigital |
R2-2006770 |
Discussion on SL relay (re)selection and authorization |
OPPO |
R2-2006843 |
View on L2/L3 SL relay |
ITL |
R2-2006855 |
Considerations for L3 UE-to-Network Relays |
Nokia, Nokia Shanghai Bell |
R2-2006861 |
NR Sidelink Relay (Re-)Selection Criterion and Procedure |
Fraunhofer IIS, Fraunhofer HHI |
R2-2006867 |
Mechanisms and Characteristics in NR Sidelink Relaying |
Fujitsu |
R2-2006962 |
Mechanisms for supporting L2-based Sidelink Relays |
AT&T |
R2-2007040 |
Selection/Authorization and Security for L2 and L3 relay |
vivo |
R2-2007041 |
Protocol stack and service continuity for L2 and L3 relay |
vivo |
R2-2007044 |
Discusssion on architecture for NR sidelink relay |
Spreadtrum Communications |
R2-2007100 |
Discussion on User Plane mechanisms for Layer 2 Relay |
Apple |
R2-2007101 |
Discussion on Control Plane mechanisms for Layer 2 Relay |
Apple |
R2-2007181 |
Overview of Layer-2 and Layer-3 sidelink relay mechanisms |
Sony |
R2-2007203 |
L3 vs L2 relaying |
Samsung Electronics GmbH |
R2-2007292 |
Considerations on L2 and L3 SL relay protocol design |
Ericsson |
R2-2007460 |
Protocol stack design for L2 relay |
Lenovo, Motorola Mobility |
R2-2007461 |
Relayed connection management |
Lenovo, Motorola Mobility |
R2-2007462 |
RRC state and CN registration of the remote UE |
Lenovo, Motorola Mobility |
R2-2007608 |
Impact on user plane protocol stack and control plane procedure for Sidelink Relay |
Intel Corporation |
R2-2007816 |
Considerations on UE-to-NW Relay |
ETRI |
R2-2008019 |
Relaying mechanism for NR sidelink |
LG Electronics Inc. |
R2-2008043 |
Consideration of Relay characteristics |
LG Electronics Inc. |
R2-2008047 |
Study aspects of UE-to-Network relay and solutions for L2 relay |
Huawei, HiSilicon |
R2-2008048 |
Service continuity for L2 UE-to-Network relay |
Huawei, HiSilicon |
R2-2008066 |
Discussion on service continuity from Uu to relay |
Xiaomi communications |
R2-2008253 |
Summary of offline discussion [604][Relay] L3 relay protocol stacks (Qualcomm) |
Qualcomm Incorporated |
R2-2008254 |
[AT111-e][605][Relay] L2 Relay Mechanism (MediaTek) |
MediaTek Inc. (Rapporteur) |
R2-2008265 |
Summary of offline discussion [604][Relay] L3 relay protocol stacks (Qualcomm) |
Qualcomm Incorporated |
R2-2008266 |
[AT111-e][605][Relay] L2 Relay Mechanism (MediaTek) |
MediaTek Inc. (Rapporteur) |
R2-2008267 |
Summary of offline discussion [604][Relay] L3 relay protocol stacks (Qualcomm) |
Qualcomm Incorporated |
R2-2008269 |
[AT111-e][605][Relay] L2 Relay Mechanism (MediaTek) |
MediaTek Inc. (Rapporteur) |
8.7.4 |
Discovery model/procedure for sidelink relaying |
|
R2-2006556 |
Discussion on relay discovery model / procedure |
Qualcomm Incorporated |
R2-2006573 |
Initiation of relaying operation |
MediaTek Inc. |
R2-2006612 |
Discovery Model/Procedure for NR Sidelink Relay |
CATT |
R2-2006738 |
Discussion on relay discovery and link management |
ZTE Corporation, Sanechips |
R2-2006761 |
Discovery Procedure for SL Relaying |
InterDigital |
R2-2006771 |
Discussion on SL relay discovery procedure |
OPPO |
R2-2006862 |
NR Sidelink Relaying Discovery |
Fraunhofer IIS, Fraunhofer HHI |
R2-2006868 |
Discovery Model and Procedure in NR Sidelink Relaying |
Fujitsu |
R2-2006931 |
On Sidelink Discovery for Relaying |
Intel Corporation |
R2-2006969 |
Sidelink relay discovery model and procedure |
Samsung Electronics Co., Ltd |
R2-2007042 |
Discussion of Relay UE discovery |
vivo |
R2-2007045 |
Discussion on discovery procedure for sidelink relay |
Spreadtrum Communications |
R2-2007098 |
Discussion on NR Sidelink Relay Discovery |
Apple, Convida Wireless |
R2-2007291 |
Discovery aspects for NR sidelink relay |
Ericsson |
R2-2007476 |
Considerations on discovery procedure for sidelink relay |
Lenovo, Motorola Mobility |
R2-2008045 |
Consideration of discovery model/procedure for sidelink relay |
LG Electronics Inc. |
R2-2008049 |
Common aspects for L2 and L3 UE-to-Network relay |
Huawei, HiSilicon |
R2-2008255 |
Discovery model and procedure |
OPPO (rapporteur) |
R2-2008270 |
RAN2 relay discovery assumptions |
RAN2 |
8.8 |
RAN slicing SI |
|
R2-2006513 |
Response to 5GC assisted cell selection for accessing network slice (R3-202558; contact: ZTE) |
RAN3 |
R2-2006527 |
Reply LS on GSMA NG.116 Attribute Area of service and impact on PLMN (S1-202294; contact: Nokia) |
SA1 |
R2-2006528 |
LS on 5GC assisted cell selection for accessing network slice (S1-202264; contact: ZTE) |
SA1 |
R2-2006529 |
LS on 5GC assisted cell selection for accessing network slice (S2-2001728; contact: ZTE) |
SA2 |
R2-2006534 |
LS on SA5 Rel-17 work on SLA (S5-203370; contact: CMCC) |
SA5 |
R2-2006632 |
Initial Discussion on the Scope and Requirements for Slicing |
CATT |
R2-2006655 |
LS on 5GC assisted cell selection for accessing network slice (S1-202264; contact: ZTE) |
SA1 |
R2-2006656 |
LS on 5GC assisted cell selection for accessing network slice (S2-2001728; contact: ZTE) |
SA2 |
R2-2006707 |
Considerations on slice aware cell selection |
KDDI Corporation |
R2-2006767 |
Discussion on RAN slicing enhancement |
Qualcomm Incorporated |
R2-2006854 |
Considerations on slice-based cell reselection |
Nokia, Nokia Shanghai Bell |
R2-2006871 |
Consideration on the scope and solutions for RAN slicing enhancement |
ZTE corporation, Sanechips |
R2-2006883 |
Considerations on scope of RAN slicing enhancements |
Lenovo, Motorola Mobility |
R2-2006887 |
5G RAN Slicing Framework During Cell Reselection |
MITRE Corporation |
R2-2006951 |
Slicing based cell (re)selection |
Intel Corporation |
R2-2006970 |
Considerations for RAN slicing |
Samsung Electronics Co., Ltd |
R2-2007051 |
Consideration on RAN slicing |
Spreadtrum Communications |
R2-2007088 |
Scoping of RAN Slicing |
Apple |
R2-2007140 |
Consideration on Rel-17 slicing |
OPPO |
R2-2007250 |
Assistant information to enable UE fast access network slice |
ITRI |
R2-2007302 |
Consideration on RAN slicing |
vivo |
R2-2007402 |
Discussion on RAN Slicing |
LG Electronics UK |
R2-2007419 |
Skeleton for TR 38.832 |
CMCC |
R2-2007420 |
Work Plan for RAN Slicing |
CMCC, ZTE |
R2-2007421 |
Discussion on support of RAN slicing |
CMCC |
R2-2007521 |
Enhancement on RAN support of network slicing |
Beijing Xiaomi Software Tech |
R2-2007606 |
Considerations on Frequency Band Selection for RAN Slicing |
SHARP Corporation |
R2-2007607 |
Basic requirements for RAN slicing |
Google Inc. |
R2-2007609 |
Discussion on Network Slicing’s Impact on Cell Reselection |
Convida Wireless |
R2-2007645 |
Methods for serving slices on different frequencies |
Ericsson |
R2-2007716 |
Scenarios and requirements for RAN slicing |
SoftBank Corp. |
R2-2007772 |
Considerations on enhancing the RAN support of network slicing |
Huawei, HiSilicon |
R2-2008071 |
Considerations scenarios on enhancing the RAN support of network slicing |
China Unicom |
R2-2008143 |
Summary of discussion [213] on Use cases and deployment scenarios (CMCC) |
CMCC |
R2-2008549 |
Draft TR 38.832 |
CMCC |
8.9.1 |
Organizational, Scope and Requirements |
|
R2-2006730 |
Views on Rel-17 NR UE power saving |
Xiaomi Communications |
R2-2006789 |
Discussion on use cases of UE power saving enhancements |
OPPO |
R2-2007189 |
RAN2 Work Plan for UE Power Saving Enhancements WI |
MediaTek Inc. |
R2-2007326 |
Discussion on RAN2 scope in Power saving |
LG Electronics. |
R2-2007436 |
Initial consideration on RAN2’s work on UE power saving |
CMCC |
R2-2007440 |
Discussion on RAN2 scope for UE Power Saving |
Huawei, HiSilicon |
8.9.2 |
Idle/inactive-mode UE power saving |
|
R2-2006608 |
Power saving enhancements for paging reception |
Qualcomm Inc |
R2-2006654 |
UE power saving for paging procedures |
ETRI |
R2-2006689 |
Coordination between RAN1 and RAN2 for paging enhancement |
vivo |
R2-2006690 |
Paging enhancement in idle inactive mode for power saving |
vivo |
R2-2006720 |
Paging enhancements to reduce UE power consumption |
Intel Corporation |
R2-2006729 |
Discussion on UE Power saving for RRC-IDLE and RRC-INACTIVE State |
Xiaomi Communications |
R2-2006774 |
Paging Enhancements to Reduce Unnecessary Paging receptions |
Samsung Electronics Co., Ltd |
R2-2006775 |
Power Consumption by RRC IDLE_INACTIVE UE |
Samsung Electronics Co., Ltd |
R2-2006790 |
Paging enhancement for power saving |
OPPO |
R2-2006874 |
Solutions to reduce unnecessary paging reception |
ZTE corporation, Sanechips |
R2-2006990 |
Considerations on paging enhancements for Power saving |
CATT |
R2-2007115 |
False Paging Mitigation |
Apple |
R2-2007116 |
Wakeup and Paging Reception |
Apple |
R2-2007182 |
Discussion on reduction unnecessary UE paging receptions |
Sony |
R2-2007190 |
Paging Enhancements for UE Power Saving in NR |
MediaTek Inc. |
R2-2007249 |
Discussion on the UE grouping based solution for idle/inactive-mode UE power saving |
ITRI |
R2-2007260 |
Paging enhancement to reduce unnecessary UE paging receptions |
Ericsson |
R2-2007261 |
Exposure of connected mode TRS occasions to Idle and Inactive mode |
Ericsson |
R2-2007437 |
Paging enhancement for idle inactive-mode UE power saving |
CMCC |
R2-2007441 |
Discussion on paging enhancements |
Huawei, HiSilicon |
R2-2007468 |
Consideration on Idle/inactive-mode UE power saving |
Lenovo, Motorola Mobility |
R2-2007562 |
Potential TRS/CSI-RS occasion(s) |
Nokia, Nokia Shanghai Bell |
R2-2007563 |
IDLE / INACTIVE mode UE power saving |
Nokia, Nokia Shanghai Bell |
R2-2007990 |
Paging enhancement for power saving |
LG Electronics Inc. |
R2-2008361 |
Paging Enhancements for UE Power Saving in NR |
MediaTek Inc. |
8.10 |
NR Non-Terrestrial Networks (NTN) |
|
R2-2008185 |
Workplan, scope and scenarios email discussion |
Thales [Moderator] |
R2-2008211 |
Workplan, scope and scenarios email discussion |
Thales [Moderator] |
R2-2008228 |
Workplan, scope and scenarios email discussion |
Thales [Moderator] |
8.10.1 |
Scope, requirements, scenarios, architecture |
|
R2-2006514 |
Response LS on the “LS out on Location of UEs and associated key issues” (R3-202824; contact: Thales) |
RAN3 |
R2-2006530 |
LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G (S2-2004688; contact: Qualcomm) |
SA2 |
R2-2006532 |
Response LS on the “LS OUT on Location of UEs and associated key issues” (S3i200056; contact: Rogers) |
SA3-LI |
R2-2006630 |
Further Clarifications on the NTN WID |
CATT |
R2-2006699 |
NR-NTN: Positioning Methods |
Fraunhofer IIS, Fraunhofer HHI |
R2-2006941 |
NTN WI- Overall Observations and Proposals |
SAMSUNG |
R2-2006971 |
Discussion of SA2 LS on fixed cell identity |
Qualcomm Inc |
R2-2006972 |
[Draft] LS Reply on SA WG2 assumptions on architecture aspects for using |
Qualcomm Inc |
R2-2007143 |
Discussion on task prioritization for NR NTN |
Huawei, HiSilicon |
R2-2007185 |
Location Services in NTN |
Sony |
R2-2007363 |
On the scenarios and simulation assumptions for evaluating NTN mobility |
Nokia, Nokia Shanghai Bell |
R2-2007431 |
Discussion on NTN workplan |
CMCC |
R2-2007519 |
Impact of pre-compensation on RACH capacity for NTN |
NEC Telecom MODUS Ltd. |
R2-2007537 |
NTN scope, scenarios, architecture, and requirements |
Ericsson |
R2-2007565 |
NR_NTN_solutions work plan |
THALES |
R2-2007572 |
NR NTN Reference scenarios definition for Rel-17 normative phase |
THALES |
R2-2007712 |
Impact of pre-compensation on RACH capacity for NTN |
NEC Telecom MODUS Ltd. |
R2-2008186 |
NR_NTN_solutions work plan |
THALES |
R2-2008212 |
[Draft] LS Reply on SA WG2 assumptions on architecture aspects for using satellite access in 5G |
Qualcomm Inc. |
R2-2008227 |
Summary of offline 115 - TP for reply LS to SA2 |
Qualcomm Inc |
R2-2008229 |
LS Reply on SA WG2 assumptions on architecture aspects for using satellite access in 5G |
RAN2 |
8.10.2 |
User Plane |
|
R2-2007105 |
On User Plane Latency reduction mechanisms in NTN Networks |
Apple |
R2-2007172 |
Discussion on UP enhancement in NTN |
Huawei, HiSilicon |
8.10.2.1 |
MAC aspects |
|
R2-2006631 |
Discussion on MAC Enhancement and Impact for NTN |
CATT |
R2-2006638 |
On Updating MAC Timers in NR-NTN |
MediaTek Inc. |
R2-2006702 |
Enhancements for NTN on MAC Layer – Impact Analysis on TS |
Nomor Research GmbH, Thales |
R2-2006781 |
Consideration on MAC enhancement for NTN |
OPPO |
R2-2006799 |
Discussion on DRX and BSR in NTN |
PANASONIC R&D Center Germany |
R2-2006927 |
MAC issues for NTN |
Intel Corporation |
R2-2006928 |
Timing advance for NTN |
Intel Corporation |
R2-2006943 |
MAC User Plane Enhancements for an NTN- Observations and Proposals |
SAMSUNG |
R2-2006974 |
UP aspects including Random Access procedure enhancements |
Qualcomm Inc |
R2-2007056 |
Introducing offsets in MAC |
Spreadtrum Communications |
R2-2007104 |
On Preamble Ambiguity in NTN Networks |
Apple |
R2-2007176 |
Discussion on UL scheduling enhancement |
Beijing Xiaomi Electronics |
R2-2007186 |
MAC enhancements in NTN |
Sony |
R2-2007397 |
Consideration on TA Precompensation |
Beijing Xiaomi Mobile Software |
R2-2007428 |
Discussion of HARQ feedback for NTN |
CMCC |
R2-2007430 |
Discussion on TA compensation |
CMCC |
R2-2007474 |
Timing advance pre-compensation in NTN |
Lenovo, Motorola Mobility |
R2-2007477 |
Discussion on DRX for NTN |
Lenovo, Motorola Mobility |
R2-2007590 |
Timing Advance, Random Access and DRX aspects in NTN |
Nokia, Nokia Shanghai Bell |
R2-2007615 |
Summary of MAC open issues in NTN |
InterDigital |
R2-2007616 |
Pre-compensation and offset calculation in NTN |
InterDigital |
R2-2007617 |
RACH preamble ambiguity in NTN |
InterDigital |
R2-2007714 |
On scheduling, HARQ, DRX, RLC, and PDCP for NTN |
Ericsson |
R2-2007715 |
On Random Access in NTN |
Ericsson |
R2-2007784 |
Consideration on MAC enhancements for NTN |
ZTE Corporation, Sanechips |
R2-2007888 |
Discussion on MAC aspects for NTN |
LG Electronics Inc. |
R2-2007995 |
MAC enhancements on the initial access procedures for NTN |
ETRI |
R2-2008101 |
Considerations on RACH procedure enhancements in NTN |
CAICT |
R2-2008188 |
[AT111][107][NTN] Pre-compensation and other MAC issues (InterDigital) |
InterDigital |
R2-2008214 |
Summary of offline 107 - Pre-compensation and other MAC issues - second round |
nterdigital |
8.10.2.2 |
Other aspects |
|
R2-2006640 |
RLC and PDCP Enhancements in NR-NTN |
MediaTek Inc. |
R2-2006703 |
Enhancements for NTN on RLC Control Loops and Timers |
Nomor Research GmbH, Thales |
R2-2006705 |
Enhancements for NTN on PDCP Control Loops and Timers |
Nomor Research GmbH, Thales |
R2-2006782 |
Consideration on RLC and PDCP enhancements for NTN |
OPPO |
R2-2007573 |
On NTN Feeder link switch over |
THALES |
R2-2007785 |
Consideration on UP timers and RLC/PDCP SN for NTN |
ZTE Corporation, Sanechips |
R2-2007889 |
Discussion on RLC and PDCP aspects for NTN |
LG Electronics Inc. |
8.10.3 |
Control Plane |
|
R2-2007103 |
On Timing Advance for NTN Networks |
Apple |
8.10.3.1 |
Idle/Inactive mode |
|
R2-2006628 |
Initial Discussion for Idle and Inactive Mode in NTN |
CATT |
R2-2006642 |
On Idle Mode Procedures in NR-NTN |
MediaTek Inc. |
R2-2006783 |
Discussion on cell reselection for NTN |
OPPO |
R2-2006821 |
Issues of the Fixed Tracking Area in NTN |
PANASONIC R&D Center Germany |
R2-2006872 |
Consideration on system information and cell (re)selection in NTN |
ZTE corporation, Sanechips |
R2-2006924 |
HAPS-Satellite ephemeris broadcast |
Loon |
R2-2006925 |
HAPS-Terrestrial PCI confusion mitigation |
Loon and Google |
R2-2006929 |
Tracking area issue for NTN |
Intel Corporation |
R2-2006945 |
Control Plane Enhancements for Idle and Inactive Modes in an NTN- Overall Observations and Proposals |
SAMSUNG |
R2-2006973 |
IDLE mode procedure |
Qualcomm Inc |
R2-2007048 |
Consideration on Celll Reselection evaluation in NTN |
Spreadtrum Communications |
R2-2007171 |
Discussion on RRC_IDLE mode issues in NTN |
Huawei, HiSilicon |
R2-2007175 |
Control Plane for Idle/Inactive mode UE |
Beijing Xiaomi Electronics |
R2-2007184 |
Idle mode enhancement in NTN |
Sony |
R2-2007251 |
Ephemeris data to be included in system information |
ITRI |
R2-2007362 |
On Tracking Areas and IDLE mode handling for NTN |
Nokia, Nokia Shanghai Bell |
R2-2007429 |
Discussion of cell selection and reselection for NTN |
CMCC |
R2-2007473 |
Ephemeris data provision in NTN |
Lenovo, Motorola Mobility |
R2-2007558 |
Idle mode aspects for NTN |
Ericsson |
R2-2007574 |
Considerations on satellite ephemeris |
THALES |
R2-2007743 |
Initial discussion on Idle mode procedures in NR NTN |
LG Electronics France |
R2-2008187 |
Offline-106: [NTN] Idle mode issues |
ZTE Corporation, Sanechips |
R2-2008213 |
Offline-106: [NTN] Idle mode issues |
ZTE Corporation, Sanechips |
8.10.3.2 |
Connected mode |
|
R2-2006547 |
Discussion on feeder link hard switch in NTN LEO |
CENC |
R2-2006552 |
Feeder link hard switch triggered HO |
CENC |
R2-2006553 |
Gateway data handling in NTN LEO |
CENC |
R2-2006629 |
Initial Discussion for Connected Mode in NTN |
CATT |
R2-2006643 |
On Connected Mode Mobility Procedures in NR-NTN |
MediaTek Inc. |
R2-2006784 |
Discussion on mobility management for connected mode UE in NTN |
OPPO |
R2-2006822 |
Overhead Reduction for the Handover Procedure in NTN |
PANASONIC R&D Center Germany |
R2-2006873 |
Consideration on mobility enhancement in NTN |
ZTE corporation, Sanechips |
R2-2006930 |
mobility enhacement for NTN |
Intel Corporation |
R2-2006953 |
Control Plane Enhancements for the Connected Mode in an NTN- Overall Observations and Proposals |
SAMSUNG |
R2-2006975 |
Connected mode mobility enhancements |
Qualcomm Inc |
R2-2007144 |
Discussion on enhancements for connected mode in NTN |
Huawei, HiSilicon |
R2-2007174 |
Control Plane for Connected mode UE |
Beijing Xiaomi Electronics |
R2-2007183 |
Mobility management in NTN |
Sony |
R2-2007463 |
Mobility management in NTN |
Lenovo, Motorola Mobility |
R2-2007601 |
Adjusting timers according to delay variations in NTN |
Nokia, Nokia Shanghai Bell |
R2-2007618 |
Location-assisted connected mobility in NTN |
InterDigital |
R2-2007744 |
Initial discussion on connected mobility in NR NTN |
LG Electronics France |
R2-2007955 |
Discussion on delay difference on measurements for NTN |
Asia Pacific Telecom co. Ltd |
8.11.1 |
Organizational |
|
R2-2006542 |
Proposed table of contents - Section 9 (positioning integrity) - TR 38.857 |
Swift Navigation, Ericsson, Intel Corporation |
R2-2006669 |
Summary on Rel-17 positioning enhancement discussion in RAN1 |
CATT, Intel Corporation, Ericsson |
R2-2006670 |
Updated Work Plan for R17 SI NR Positioning Enhancements |
CATT, Intel Corporation, Ericsson |
R2-2006671 |
Skeleton proposals for TR38.857 |
CATT |
R2-2006749 |
Handling on Rel-16 leftover issue in Rel-17 |
Intel Corporation |
R2-2006958 |
skeleton for TR38857 |
Ericsson |
8.11.2 |
Enhancements for commercial use cases |
|
R2-2006567 |
Discussion on potential positioning enhancement |
vivo |
R2-2006578 |
Discussion on R17 positioning enhancement |
Huawei, HiSilicon |
R2-2006672 |
Discussion on ehancements for commercial use cases |
CATT |
R2-2006750 |
Consideration on the support of low latency requirement |
Intel Corporation |
R2-2006956 |
Enhancements for commercial use cases |
Ericsson |
R2-2007049 |
Discussion on positioning enhancements for commercial use cases |
Spreadtrum Communications |
R2-2007128 |
On-demand PRS transmission and dynamic PRS resource allocation |
Nokia, Nokia Shanghai Bell |
R2-2007157 |
Positioning for UE in RRC Idle and Inactive state |
OPPO |
R2-2007159 |
Discussion on on-demand DL-PRS |
OPPO |
R2-2007170 |
Discussion on PRS enhancements |
Beijing Xiaomi Electronics |
R2-2007173 |
Positioning enhancements for RRC IDLE and RRC INACTIVE state UE |
Beijing Xiaomi Electronics |
R2-2007587 |
End-to-end latency reduction for DL/UL positioning |
InterDigital, Inc. |
R2-2007629 |
NR Positioning Enhancements |
Qualcomm Incorporated |
R2-2007694 |
On-demand PRS transmission and dynamic PRS resource allocation |
Nokia, Nokia Shanghai Bell |
R2-2008261 |
[AT111-e][612][POS] Assumptions for analysis of commercial use cases (Ericsson) |
Ericsson |
8.11.3 |
Integrity and reliability of assistance data and position information |
|
R2-2006541 |
TP for Study on Positioning Integrity and Reliability |
Swift Navigation, Deutsche Telekom, u-blox, Ericsson, Mitsubishi Electric, Intel Corporation, CATT, UIC |
8.11.3.1 |
KPIs and use cases |
|
R2-2006564 |
Identify positioning integrity use case and KPIs |
vivo |
R2-2006579 |
Discussion on positioning integrity KPIs and relevant use cases |
Huawei, HiSilicon |
R2-2006673 |
Discussion on integrity KPIs and use cases |
CATT |
R2-2006754 |
Consideration on positioning integrity |
Intel Corporation |
R2-2006954 |
Positioning integrity KPIs and support for RAT dependent use cases |
Ericsson |
R2-2007050 |
Discussion on positioning integrity KPIs and use cases |
Spreadtrum Communications |
R2-2007073 |
Discussion on integrity and reliability for positioning based on an IIoT use case |
Sumitomo Elec. Industries, Ltd |
R2-2007102 |
Discussion on Positioning Integrity |
Apple |
R2-2007158 |
Discussion on the KPIs of integrity |
OPPO |
R2-2007187 |
Discussion on Integrity of positioning information |
Sony |
R2-2007646 |
Discussion on use cases and KPIs for position integrity |
ESA |
R2-2007936 |
Discussion of the positioning integrity definition |
ZTE Corporation, Sanechips |
R2-2007937 |
Discussion of the integrity events and integrity failure |
ZTE Corporation, Sanechips |
R2-2008256 |
[AT111-e][607][POS] Summary of email discussion on Integrity definitions, KPIs, and use cases (Swift) |
Swift Navigation |
R2-2008262 |
[AT111-e][607][POS] Summary of email discussion on Integrity definitions, KPIs, and use cases (Swift) |
Swift Navigation |
8.11.3.2 |
Error sources, threat models, occurrence rates and failure modes |
|
R2-2006565 |
Identify Error sources for positioning integrity |
vivo |
R2-2006580 |
Discussion on positioning integrity validation and reporting |
Huawei, HiSilicon |
R2-2006674 |
Discussion on error sources, threat models, occurrence rates and failure modes |
CATT |
R2-2006955 |
Factors impacting positioning integrity |
Ericsson |
R2-2007647 |
Discussion on GNSS position integrity error sources |
ESA |
R2-2007938 |
Discussion of the positioning error sources, threat models and failure modes |
ZTE Corporation, Sanechips |
R2-2008263 |
[AT111-e][613][POS] Integrity Error Sources (Huawei) |
Huawei, HiSilicon |
R2-2008613 |
LS to RAN1 on the error source for RAT-dependent positioning |
Huawei, HiSilicon |
R2-2008649 |
LS on the error source for RAT-dependent positioning |
RAN2 |
8.11.3.3 |
Methodologies for network-assisted and UE-assisted integrity |
|
R2-2006566 |
Discussion on positioning integrity methodologies |
vivo |
R2-2006581 |
Discussion for network-assisted and UE-assisted integrity |
Huawei, HiSilicon |
R2-2006675 |
Discussion on methodologies for network-assisted and UE-assisted integrity |
CATT |
R2-2006957 |
LPP signalling for integrity support of RAT dependent positioning |
Ericsson |
R2-2007160 |
Discussion on methodologies for UE-based and UE-assisted integrity |
OPPO |
R2-2007238 |
Reporting movement model |
Fraunhofer IIS, Fraunhofer HHI |
R2-2007246 |
Reporting the situational quality of RAT and RAT-independent technologies |
Fraunhofer IIS, Fraunhofer HHI |
R2-2007588 |
Methodologies for network-assisted and UE-assisted integrity |
InterDigital, Inc. |
R2-2007656 |
Discussion on methodologies for position integrity |
ESA |
R2-2007939 |
Discussion of the methodologies for network-assisted and UE-assisted integrity |
ZTE Corporation, Sanechips |
8.12.1 |
Organizational and scope |
|
R2-2006732 |
General views on Higher-layer impacts for Redcap devices |
Xiaomi Communications |
R2-2006753 |
RAN1-2 work scope discussion on RedCap capability |
Intel Corporation |
R2-2006910 |
Scope of RedCap SI |
Ericsson |
R2-2006978 |
Expected RAN2 scope of RedCap |
NEC |
R2-2007366 |
TR38.875 skeleton updates for Study on support of reduced capability NR devices |
Ericsson |
R2-2008189 |
Summary of [AT111][108][REDCAP] Scope and skeleton update |
Rapporteur (Ericsson) |
R2-2008190 |
TR38.875 skeleton updates for Study on support of reduced capability NR devices |
Ericsson |
8.12.2.1 |
Principles for how to define and constrain reduced capabilities |
|
R2-2006605 |
Defining and constraining UEs with reduced capabilities |
Qualcomm Inc |
R2-2006660 |
Capability and initial access of RedCap UEs |
Samsung |
R2-2006691 |
UE type and capability for RedCap UEs |
vivo, Guangdong Genius |
R2-2006733 |
Discussion on UE Capaiblity Issues for reduced capability NR devices |
Xiaomi Communications |
R2-2006751 |
Reduced capability signalling framework |
Intel Corporation |
R2-2006785 |
Discussion on definition of RedCap Ues |
OPPO |
R2-2006903 |
Define and constrain reduced capability |
ZTE Corporation, Sanechips |
R2-2006911 |
Framework and Principles for Reduced Capability |
Ericsson |
R2-2007011 |
On definition and constraint of reduced capabilities |
CATT |
R2-2007110 |
RedCap UE characterization and access restriction |
Apple |
R2-2007344 |
Capability definition of REDCAP UE |
Huawei, HiSilicon |
R2-2007400 |
Discussion on how to define reduced capability devices |
LG Electronics UK |
R2-2007478 |
The principle to constrain reduced capability NR devices |
Lenovo, Motorola Mobility |
R2-2007490 |
Principles for reduced capabilities |
Nokia, Nokia Shanghai Bell |
R2-2007492 |
On the definition of a RedCap device type |
MediaTek Inc. |
R2-2008191 |
Summary of discussion [109][REDCAP] Reduced capability signalling framework (Intel) |
Intel Corporation |
8.12.2.2 |
Identification and access restrictions |
|
R2-2006606 |
Identification and access restriction for RedCap UEs |
Qualcomm Inc |
R2-2006661 |
Coexistence between legacy UEs and RedCap UEs |
Samsung |
R2-2006692 |
Identification and access restrictions for RedCap UEs |
vivo, Guangdong Genius |
R2-2006734 |
Discussion on Identification and UE access restrictions for Redcap devices |
Xiaomi Communications |
R2-2006752 |
Identification and Access restriction for RedCap devices |
Intel Corporation |
R2-2006786 |
Discussion on RedCap UE’s identification and access control |
OPPO |
R2-2006904 |
Identification and access control for Redcap UE |
ZTE Corporation, Sanechips |
R2-2006912 |
Identification and access restriction for devices with reduced capabilities |
Ericsson |
R2-2006979 |
Constraint on usage of RedCap functions |
NEC |
R2-2007012 |
Identification and access restrictions for reduced capability UE |
CATT |
R2-2007345 |
Identification and access restriction of REDCAP UE |
Huawei, HiSilicon |
R2-2007399 |
Access restriction for reduced capability devices |
LG Electronics UK |
R2-2007480 |
Discussion on the identification of Redcap |
Lenovo, Motorola Mobility |
R2-2007491 |
Cell access for REDCAP UE with reduced bandwidth |
Nokia, Nokia Shanghai Bell |
R2-2007493 |
On UE identification and access restrictions |
MediaTek Inc. |
R2-2007560 |
Cell access restrictions for REDCAP UE |
Nokia, Nokia Shanghai Bell |
R2-2008192 |
Summary of offline 110 - Identification and access restriction |
Huawei |
8.12.3 |
UE power saving and battery lifetime enhancement |
|
R2-2006607 |
Power saving enhancements for RedCap UEs |
Qualcomm Inc |
R2-2006662 |
RRM relaxation for stationary devices |
Samsung |
R2-2006693 |
RRM relaxation for power saving |
vivo, Guangdong Genius |
R2-2006694 |
DRX enhancement for RedCap UEs |
vivo, Guangdong Genius |
R2-2006731 |
Discussion on UE Power saving for Redcap Devices |
Xiaomi Communications |
R2-2006748 |
Use cases target to extend paging DRX cycle and relax measurements for stationary devices |
Intel Corporation |
R2-2006787 |
Consideration on extended DRX for RedCap |
OPPO |
R2-2006788 |
Discussion on RRM relaxation |
OPPO |
R2-2006902 |
Consideration on RRM relaxation for Redcap UE |
ZTE Corporation, Sanechips |
R2-2006905 |
Introduction of eDRX for Redcap UE |
ZTE Corporation, Sanechips |
R2-2006913 |
Reducing power consumption in RedCap devices |
Ericsson |
R2-2007013 |
eDRX for NR RRC Inactive and Idle States |
CATT |
R2-2007111 |
Impact of power-saving aspects on RedCap UEs |
Apple |
R2-2007346 |
Discussion on eDRX for RRC_INACTIVE and RRC_IDLE |
Huawei, HiSilicon |
R2-2007347 |
RRM measurement relaxation for REDCAP UE |
Huawei, HiSilicon |
R2-2007393 |
Introducing Extended DRX for RRC Inactive and/or Idle |
Samsung |
R2-2007401 |
Extended DRX for reduced capability devices in RRC_IDLE and RRC_INACTIVE |
LG Electronics UK |
R2-2007470 |
eDRX for Idel/inactive-mode UE with reduced capability |
Lenovo, Motorola Mobility |
R2-2007471 |
RRM relaxation for stationary UE with reduced capability |
Lenovo, Motorola Mobility |
R2-2007494 |
eDRX for reduced capability UEs |
MediaTek Inc. |
R2-2007561 |
Power saving and battery lifetime enhancement for REDCAP UE |
Nokia, Nokia Shanghai Bell |
R2-2007653 |
eDRX for Reduced Capability NR Devices |
Convida Wireless |
R2-2007654 |
Discussion on eDRX Configuration |
Convida Wireless |
R2-2007745 |
Considerations on RRM for reduced capability UEs |
LG Electronics France |
R2-2008130 |
Reducing power consumption in RedCap devices |
Ericsson |
R2-2008193 |
Summary of offline 111 - DRX aspects (CATT) |
CATT |
R2-2008216 |
Summary of offline 111 - DRX aspects - second round |
CATT |
8.13.1 |
Organizational |
|
R2-2007996 |
Work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI |
CMCC, Ericsson |
R2-2008116 |
Work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI |
CMCC, Ericsson |
8.13.2 |
SON, RAN2 scope and requirements |
|
R2-2006651 |
Clarification for SON Scope and Use Cases |
CATT |
R2-2006678 |
Discussion on rel-17 Radio Link Failure Report |
NTT DOCOMO INC. |
R2-2006746 |
Mobility support in SON/MDT for Rel17 |
Intel Corporation |
R2-2007071 |
Open Issues in SON |
QUALCOMM Incorporated |
R2-2007155 |
Enhancements and scope of R17 SON |
OPPO |
R2-2007196 |
SON for Rel-16 mobility enhancement |
NEC |
R2-2007301 |
Discussion on SON enhancements |
vivo |
R2-2007392 |
Optimization for Rel-16 Features |
Samsung |
R2-2007435 |
SON Consideration for R16 Mobility Enhancement |
CMCC |
R2-2007464 |
MRO for Inter-RAT handover |
Lenovo, Motorola Mobility |
R2-2007465 |
MRO for CHO and DAPS Handover |
Lenovo, Motorola Mobility |
R2-2007516 |
Rel-17 SON enhancements scope |
Nokia, Nokia Shanghai Bell |
R2-2007661 |
SON Scope and Requirements for Rel.17 |
Ericsson |
R2-2007662 |
SON Summary |
Ericsson |
R2-2007769 |
Discussion for RAN2 SON scope and requirements |
Huawei, HiSilicon |
R2-2007782 |
Consideration on SON enhancements |
ZTE Corporation, Sanechips |
R2-2008288 |
SON Summary |
Ericsson |
8.13.3 |
MDT Scope and requirements |
|
R2-2006652 |
Clarification for MDT Scope and Use Cases |
CATT |
R2-2006747 |
Scope of MDT for Rel17 |
Intel Corporation |
R2-2007070 |
Open Issues in MDT |
QUALCOMM Europe Inc. - Spain |
R2-2007072 |
Open Issues in MDT |
Qualcomm Incorporated |
R2-2007156 |
Enhancements and scope of R17 MDT |
OPPO |
R2-2007233 |
R17 MDT scope for MR-DC and early measurments |
Samsung Telecommunications |
R2-2007300 |
Discussion on MDT enhancements |
vivo |
R2-2007434 |
MDT Enhancement for 2-step RA |
CMCC |
R2-2007515 |
Rel-17 MDT enhancements scope |
Nokia, Nokia Shanghai Bell |
R2-2007667 |
MDT scope and requirements |
Ericsson |
R2-2007770 |
Discussion for MDT |
Huawei, HiSilicon |
R2-2007771 |
Summary on 8.13.3 MDT |
Huawei, HiSilicon |
R2-2007783 |
Consideration on MDT enhancements |
ZTE Corporation, Sanechips |
8.14 |
NR QoE SI |
|
R2-2007081 |
NR QoE management |
Samsung Electronics |
R2-2007600 |
NR QoE Measurement Triggering, Configuration, Collection and Reporting |
Ericsson |
R2-2007768 |
Discussion for NR QoE |
Huawei, HiSilicon |
R2-2007940 |
Discussion on QoE in NR |
ZTE Corporation, Sanechips |
8.16 |
NR R17 Other |
|
R2-2006536 |
LS on Requirements on positioning for UAS (S6-200269; contact: InterDigital) |
SA6 |
R2-2006537 |
Reply LS to extend the scope of eV2X (SP-191379; contact: Telecom Italia) |
SA |
9.1 |
NB-IoT and eMTC enhancements |
|
R2-2008309 |
RAN2 agreements for Rel-17 NB-IoT and LTE-MTC |
Document Rapporteur (Ericsson) |
9.1.1 |
Organizational |
|
R2-2007696 |
Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC |
Ericsson, Huawei |
9.1.2 |
NB-IoT neighbor cell measurements and corresponding measurement triggering before RLF |
|
R2-2006833 |
Reducing time taken for reestablishment procedures in NB-IOT |
Ericsson |
R2-2006834 |
Cell measurement in connected mode for NB-IoT |
ZTE Corporation, Sanechips |
R2-2007342 |
Discussion on RLF enhancements |
Huawei, HiSilicon |
R2-2007472 |
Neighbor cell measurements triggering before RLF |
Lenovo, Motorola Mobility |
R2-2007569 |
Connected mode neighbor cell measurement in NB-IoT |
Qualcomm Incorporated |
R2-2007619 |
Clarification on Agenda Item – 9.1.2 |
THALES |
R2-2007951 |
Measurement before radio link failure |
Shanghai Chen Si Electronics |
R2-2008097 |
Analysis on Re-establishment time reduction |
Nokia, Nokia Shanghai Bell |
R2-2008310 |
Report of [AT111-e][308][NBIOT/eMTC R17] RLF enhancements |
Qualcomm Incorporated |
9.1.3 |
NB-IoT carrier selection based on the coverage level, and associated carrier specific configuration |
|
R2-2006832 |
NB-IoT carrier selection and configuration based on coverage level |
Ericsson |
R2-2006835 |
Enhancements on multi carrier configuration and selection |
ZTE Corporation, Sanechips |
R2-2007343 |
Use cases and scenarios of carrier specific configuration |
Huawei, HiSilicon |
R2-2007354 |
Analysis on carrier selection options |
Nokia, Nokia Shanghai Bell |
R2-2007570 |
Support for NB-IoT carrier selection based on the coverage level |
Qualcomm Incorporated |
R2-2007957 |
Carrier selection enhancement |
Shanghai Chen Si Electronics |
R2-2008311 |
[AT111-e][309][NBIOT/eMTC R17] Carrier selection (Ericsson) |
Ericsson |
10.1 |
Session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing |
|
R2-2008121 |
Report on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing |
Vice Chairman (Nokia) |
10.2 |
Session on R16 eMIMO, CLI, PRN, RACS and R17 NTN and RedCap |
|
R2-2008122 |
Report from Break-out session on R16 eMIMO, CLI, PRN, RACS and R17 NTN and RedCap |
Vice Chairman (ZTE) |
10.3 |
Session on eMTC |
|
R2-2008123 |
Report eMTC breakout session |
Session chair (Ericsson) |
10.4 |
Session on NR-U, Power Savings, NTN and 2-step RACH |
|
R2-2008124 |
Session minutes for NR-U, Power Savings, NTN and 2-step RACH |
Session chair (InterDigital) |
10.5 |
Session on positioning and sidelink relay |
|
R2-2008125 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
10.6 |
Session on SON/MDT |
|
R2-2008126 |
Report from SOM/MDT session |
Session chair (CMCC) |
10.7 |
Session on NB-IoT |
|
R2-2008127 |
Report NB-IoT breakout session |
Session chair (Huawei) |
10.8 |
Session on LTE V2X and NR V2X |
|
R2-2008128 |
Report from session on LTE V2X and NR V2X |
Session chair (Samsung) |
R2-2008561 |
Report from session on LTE V2X and NR V2X |
Session chair (Samsung) |